Supporting spatial division multiplexing operation in integrated access and backhaul networks

ABSTRACT

The systems and methods described herein support efficient SDM operation in IAB networks. A first node receives a semi-static resource allocation from a CU based on at least one multiplexing capability of the first node. The first node also receives from the CU one or more resource conditions for using allocated resources of the semi-static resource allocation, and the first node communicates with a second node based on the semi-static resource allocation and the one or more resource conditions. The at least one multiplexing capability includes at least one of SDM or FDM, including full duplex or half duplex. The at least one multiplexing capability is also with respect to one or more transmission direction combinations of the first node.

CROSS REFERENCE TO RELATED APPLICATION(S)

This application claims the benefit of U.S. Provisional Application Ser.No. 62/836,506, entitled “SUPPORTING SPATIAL DIVISION MULTIPLEXINGOPERATION IN INTEGRATED ACCESS AND BACKHAUL NETWORKS” and filed on Apr.19, 2019, which is expressly incorporated by reference herein in itsentirety.

BACKGROUND Technical Field

The present disclosure relates generally to communication systems, andmore particularly, to a wireless communication system between anintegrated access and backhaul (IAB) node or user equipment (UE) and acentral unit (CU).

INTRODUCTION

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources. Examples of suchmultiple-access technologies include code division multiple access(CDMA) systems, time division multiple access (TDMA) systems, frequencydivision multiple access (FDMA) systems, orthogonal frequency divisionmultiple access (OFDMA) systems, single-carrier frequency divisionmultiple access (SC-FDMA) systems, and time division synchronous codedivision multiple access (TD-SCDMA) systems.

These multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent wireless devices to communicate on a municipal, national,regional, and even global level. An example telecommunication standardis 5G New Radio (NR). 5G NR is part of a continuous mobile broadbandevolution promulgated by Third Generation Partnership Project (3GPP) tomeet new requirements associated with latency, reliability, security,scalability (e.g., with Internet of Things (IoT)), and otherrequirements. 5G NR includes services associated with enhanced mobilebroadband (eMBB), massive machine type communications (mMTC), and ultrareliable low latency communications (URLLC). Some aspects of 5G NR maybe based on the 4G Long Term Evolution (LTE) standard. There exists aneed for further improvements in 5G NR technology. These improvementsmay also be applicable to other multi-access technologies and thetelecommunication standards that employ these technologies.

SUMMARY

The following presents a simplified summary of one or more aspects inorder to provide a basic understanding of such aspects. This summary isnot an extensive overview of all contemplated aspects, and is intendedto neither identify key or critical elements of all aspects nordelineate the scope of any or all aspects. Its sole purpose is topresent some concepts of one or more aspects in a simplified form as aprelude to the more detailed description that is presented later.

In an aspect of the disclosure, a method, a computer-readable medium,and an apparatus are provided. The apparatus may be a first node. Theapparatus transmits a report to a central unit (CU), where the reportincludes at least one multiplexing capability of the first node orincludes at least one multiplexing capability condition for the at leastone multiplexing capability of the first node. The apparatus receives asemi-static resource allocation from the CU based on the at least onemultiplexing capability, and communicates with a second node based onthe semi-static resource allocation. The at least one multiplexingcapability comprises at least one of Spatial Division Multiplexing (SDM)or Frequency Division Multiplexing (FDM), and the SDM includes at leastone of SDM Full Duplex (SDM FD) or SDM Half-Duplex (SDM HD). The atleast one multiplexing capability is also with respect to one or moretransmission direction combinations of the first node.

In an aspect of the disclosure, a method, a computer-readable medium,and an apparatus are provided. The apparatus may be a CU. The apparatusreceives a report from a first node, where the report includes at leastone multiplexing capability of the first node or includes at least onemultiplexing capability condition for the at least one multiplexingcapability of the first node. The apparatus transmits to the first nodea semi-static resource allocation based on the at least one multiplexingcapability for communication of the first node with a second node, wherethe at least one multiplexing capability comprises at least one of SDMor FDM, and where the SDM includes at least one of SDM FD or SDM HD. Theat least one multiplexing capability is also with respect to one or moretransmission direction combinations of the first node.

In an aspect of the disclosure, a method, a computer-readable medium,and an apparatus are provided. The apparatus may be a first node. Theapparatus receives a semi-static resource allocation from a CU based onat least one multiplexing capability of the first node. The apparatusalso receives, from the CU, one or more resource conditions for usingallocated resources of the semi-static resource allocation, andcommunicates with a second node based on the semi-static resourceallocation and the one or more resource conditions. The at least onemultiplexing capability comprises at least one of Spatial DivisionMultiplexing (SDM) or Frequency Division Multiplexing (FDM), and the SDMincludes at least one of SDM Full Duplex (SDM FD) or SDM Half-Duplex(SDM HD). The at least one multiplexing capability is also with respectto one or more transmission direction combinations of the first node.

In an aspect of the disclosure, a method, a computer-readable medium,and an apparatus are provided. The apparatus may be a CU. The apparatustransmits to a first node a semi-static resource allocation based on atleast one multiplexing capability of the first node for communication ofthe first node with a second node. The apparatus also transmits, to thefirst node, one or more resource conditions for using allocatedresources of the semi-static resource allocation, where thecommunication of the first node with the second node is based on the oneor more resource conditions. The at least one multiplexing capabilitycomprises at least one of SDM or FDM, and the SDM includes at least oneof SDM FD or SDM HD. The at least one multiplexing capability is alsowith respect to one or more transmission direction combinations of thefirst node.

In an aspect of the disclosure, a method, a computer-readable medium,and an apparatus are provided. The apparatus may be a first node. Theapparatus receives a semi-static resource allocation from a CU based onat least one multiplexing capability of the first node. The apparatuscommunicates with a second node based on the semi-static resourceallocation. The apparatus also transmits a change request to the CU tomodify the semi-static resource allocation. The at least onemultiplexing capability comprises at least one of Spatial DivisionMultiplexing (SDM) or Frequency Division Multiplexing (FDM), and the SDMincludes at least one of SDM Full Duplex (SDM FD) or SDM Half-Duplex(SDM HD). The at least one multiplexing capability is also with respectto one or more transmission direction combinations of the first node.

In an aspect of the disclosure, a method, a computer-readable medium,and an apparatus are provided. The apparatus may be a CU. The apparatustransmits to a first node a semi-static resource allocation based on atleast one multiplexing capability of the first node for communication ofthe first node with a second node. The apparatus also receives a changerequest from the first node to modify the semi-static resourceallocation. The at least one multiplexing capability comprises at leastone of SDM or FDM, and the SDM includes at least one of SDM FD or SDMHD. The at least one multiplexing capability is also with respect to oneor more transmission direction combinations of the first node.

To the accomplishment of the foregoing and related ends, the one or moreaspects comprise the features hereinafter fully described andparticularly pointed out in the claims. The following description andthe annexed drawings set forth in detail certain illustrative featuresof the one or more aspects. These features are indicative, however, ofbut a few of the various ways in which the principles of various aspectsmay be employed, and this description is intended to include all suchaspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a wireless communicationssystem and an access network.

FIGS. 2A, 2B, 2C, and 2D are diagrams illustrating examples of a first5G/NR frame, DL channels within a 5G/NR subframe, a second 5G/NR frame,and UL channels within a 5G/NR subframe, respectively.

FIG. 3 is a diagram illustrating an example of a base station and userequipment (UE) in an access network.

FIG. 4 is a diagram illustrating various examples of IAB nodecommunication.

FIG. 5 is a diagram illustrating additional examples of IAB nodecommunication.

FIG. 6 is a diagram illustrating another example of IAB nodecommunication.

FIG. 7 is a call flow diagram illustrating an example of wirelesscommunication between a parent node, a child node, and a CU.

FIG. 8 is a call flow diagram illustrating another example of wirelesscommunication between a parent node, a child node, and a CU.

FIG. 9 is a diagram illustrating a further example of IAB nodecommunication.

FIG. 10 is a flowchart of a method of wireless communication at a firstnode.

FIG. 11 is a conceptual data flow diagram illustrating the data flowbetween different means/components in an example apparatus.

FIG. 12 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

FIG. 13 is a flowchart of a method of wireless communication at a CU.

FIG. 14 is a conceptual data flow diagram illustrating the data flowbetween different means/components in an example apparatus.

FIG. 15 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

FIG. 16 is a flowchart of a method of wireless communication at a firstnode.

FIG. 17 is a conceptual data flow diagram illustrating the data flowbetween different means/components in an example apparatus.

FIG. 18 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

FIG. 19 is a flowchart of a method of wireless communication at a CU.

FIG. 20 is a conceptual data flow diagram illustrating the data flowbetween different means/components in an example apparatus.

FIG. 21 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

FIG. 22 is a flowchart of a method of wireless communication at a firstnode.

FIG. 23 is a conceptual data flow diagram illustrating the data flowbetween different means/components in an example apparatus.

FIG. 24 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

FIG. 25 is a flowchart of a method of wireless communication at a CU.

FIG. 26 is a conceptual data flow diagram illustrating the data flowbetween different means/components in an example apparatus.

FIG. 27 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

DETAILED DESCRIPTION

The detailed description set forth below in connection with the appendeddrawings is intended as a description of various configurations and isnot intended to represent the only configurations in which the conceptsdescribed herein may be practiced. The detailed description includesspecific details for the purpose of providing a thorough understandingof various concepts. However, it will be apparent to those skilled inthe art that these concepts may be practiced without these specificdetails. In some instances, well known structures and components areshown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunication systems will now be presented withreference to various apparatus and methods. These apparatus and methodswill be described in the following detailed description and illustratedin the accompanying drawings by various blocks, components, circuits,processes, algorithms, etc. (collectively referred to as “elements”).These elements may be implemented using electronic hardware, computersoftware, or any combination thereof. Whether such elements areimplemented as hardware or software depends upon the particularapplication and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or anycombination of elements may be implemented as a “processing system” thatincludes one or more processors. Examples of processors includemicroprocessors, microcontrollers, graphics processing units (GPUs),central processing units (CPUs), application processors, digital signalprocessors (DSPs), reduced instruction set computing (RISC) processors,systems on a chip (SoC), baseband processors, field programmable gatearrays (FPGAs), programmable logic devices (PLDs), state machines, gatedlogic, discrete hardware circuits, and other suitable hardwareconfigured to perform the various functionality described throughoutthis disclosure. One or more processors in the processing system mayexecute software. Software shall be construed broadly to meaninstructions, instruction sets, code, code segments, program code,programs, subprograms, software components, applications, softwareapplications, software packages, routines, subroutines, objects,executables, threads of execution, procedures, functions, etc., whetherreferred to as software, firmware, middleware, microcode, hardwaredescription language, or otherwise.

Accordingly, in one or more example embodiments, the functions describedmay be implemented in hardware, software, or any combination thereof. Ifimplemented in software, the functions may be stored on or encoded asone or more instructions or code on a computer-readable medium.Computer-readable media includes computer storage media. Storage mediamay be any available media that can be accessed by a computer. By way ofexample, and not limitation, such computer-readable media can comprise arandom-access memory (RAM), a read-only memory (ROM), an electricallyerasable programmable ROM (EEPROM), optical disk storage, magnetic diskstorage, other magnetic storage devices, combinations of theaforementioned types of computer-readable media, or any other mediumthat can be used to store computer executable code in the form ofinstructions or data structures that can be accessed by a computer.

FIG. 1 is a diagram illustrating an example of a wireless communicationssystem and an access network 100. The wireless communications system(also referred to as a wireless wide area network (WWAN)) includes basestations 102, UEs 104, an Evolved Packet Core (EPC) 160, and anothercore network 190 (e.g., a 5G Core (5GC)). The base stations 102 mayinclude macrocells (high power cellular base station) and/or small cells(low power cellular base station). The macrocells include base stations.The small cells include femtocells, picocells, and microcells.

The base stations 102 configured for 4G LTE (collectively referred to asEvolved Universal Mobile Telecommunications System (UMTS) TerrestrialRadio Access Network (E-UTRAN)) may interface with the EPC 160 throughfirst backhaul links 132 (e.g., S1 interface). The base stations 102configured for 5G NR (collectively referred to as Next Generation RAN(NG-RAN)) may interface with core network 190 through second backhaullinks 184. In addition to other functions, the base stations 102 mayperform one or more of the following functions: transfer of user data,radio channel ciphering and deciphering, integrity protection, headercompression, mobility control functions (e.g., handover, dualconnectivity), inter-cell interference coordination, connection setupand release, load balancing, distribution for non-access stratum (NAS)messages, NAS node selection, synchronization, radio access network(RAN) sharing, multimedia broadcast multicast service (MBMS), subscriberand equipment trace, RAN information management (RIM), paging,positioning, and delivery of warning messages. The base stations 102 maycommunicate directly or indirectly (e.g., through the EPC 160 or corenetwork 190) with each other over third backhaul links 134 (e.g., X2interface). The third backhaul links 134 may be wired or wireless.

The base stations 102 may wirelessly communicate with the UEs 104. Eachof the base stations 102 may provide communication coverage for arespective geographic coverage area 110. There may be overlappinggeographic coverage areas 110. For example, the small cell 102′ may havea coverage area 110′ that overlaps the coverage area 110 of one or moremacro base stations 102. A network that includes both small cell andmacrocells may be known as a heterogeneous network. A heterogeneousnetwork may also include Home Evolved Node Bs (eNBs) (HeNBs), which mayprovide service to a restricted group known as a closed subscriber group(CSG). The communication links 120 between the base stations 102 and theUEs 104 may include uplink (UL) (also referred to as reverse link)transmissions from a UE 104 to a base station 102 and/or downlink (DL)(also referred to as forward link) transmissions from a base station 102to a UE 104. The communication links 120 may use multiple-input andmultiple-output (MIMO) antenna technology, including spatialmultiplexing, beamforming, and/or transmit diversity. The communicationlinks may be through one or more carriers. The base stations 102/UEs 104may use spectrum up to YMHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz)bandwidth per carrier allocated in a carrier aggregation of up to atotal of Yx MHz (x component carriers) used for transmission in eachdirection. The carriers may or may not be adjacent to each other.Allocation of carriers may be asymmetric with respect to DL and UL(e.g., more or fewer carriers may be allocated for DL than for UL). Thecomponent carriers may include a primary component carrier and one ormore secondary component carriers. A primary component carrier may bereferred to as a primary cell (PCell) and a secondary component carriermay be referred to as a secondary cell (SCell).

Certain UEs 104 may communicate with each other using device-to-device(D2D) communication link 158. The D2D communication link 158 may use theDL/UL WWAN spectrum. The D2D communication link 158 may use one or moresidelink channels, such as a physical sidelink broadcast channel(PSBCH), a physical sidelink discovery channel (PSDCH), a physicalsidelink shared channel (PSSCH), and a physical sidelink control channel(PSCCH). D2D communication may be through a variety of wireless D2Dcommunications systems, such as for example, FlashLinQ, WiMedia,Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

The wireless communications system may further include a Wi-Fi accesspoint (AP) 150 in communication with Wi-Fi stations (STAs) 152 viacommunication links 154 in a 5 GHz unlicensed frequency spectrum. Whencommunicating in an unlicensed frequency spectrum, the STAs 152/AP 150may perform a clear channel assessment (CCA) prior to communicating inorder to determine whether the channel is available.

The small cell 102′ may operate in a licensed and/or an unlicensedfrequency spectrum. When operating in an unlicensed frequency spectrum,the small cell 102′ may employ NR and use the same 5 GHz unlicensedfrequency spectrum as used by the Wi-Fi AP 150. The small cell 102′,employing NR in an unlicensed frequency spectrum, may boost coverage toand/or increase capacity of the access network.

A base station 102, whether a small cell 102′ or a large cell (e.g.,macro base station), may include and/or be referred to as an eNB, gNodeB(gNB), or another type of base station. Some base stations, such as gNB180 may operate in a traditional sub 6 GHz spectrum, in millimeter wave(mmW) frequencies, and/or near mmW frequencies in communication with theUE 104. When the gNB 180 operates in mmW or near mmW frequencies, thegNB 180 may be referred to as an mmW base station. Extremely highfrequency (EHF) is part of the RF in the electromagnetic spectrum. EHFhas a range of 30 GHz to 300 GHz and a wavelength between 1 millimeterand 10 millimeters. Radio waves in the band may be referred to as amillimeter wave. Near mmW may extend down to a frequency of 3 GHz with awavelength of 100 millimeters. The super high frequency (SHF) bandextends between 3 GHz and 30 GHz, also referred to as centimeter wave.Communications using the mmW/near mmW radio frequency band (e.g., 3GHz-300 GHz) has extremely high path loss and a short range. The mmWbase station 180 may utilize beamforming 182 with the UE 104 tocompensate for the extremely high path loss and short range. The basestation 180 and the UE 104 may each include a plurality of antennas,such as antenna elements, antenna panels, and/or antenna arrays tofacilitate the beamforming.

The base station 180 may transmit a beamformed signal to the UE 104 inone or more transmit directions 182′. The UE 104 may receive thebeamformed signal from the base station 180 in one or more receivedirections 182″. The UE 104 may also transmit a beamformed signal to thebase station 180 in one or more transmit directions. The base station180 may receive the beamformed signal from the UE 104 in one or morereceive directions. The base station 180/UE 104 may perform beamtraining to determine the best receive and transmit directions for eachof the base station 180/UE 104. The transmit and receive directions forthe base station 180 may or may not be the same. The transmit andreceive directions for the UE 104 may or may not be the same.

The EPC 160 may include a Mobility Management Entity (MME) 162, otherMMEs 164, a Serving Gateway 166, a Multimedia Broadcast MulticastService (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC)170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be incommunication with a Home Subscriber Server (HSS) 174. The MME 162 isthe control node that processes the signaling between the UEs 104 andthe EPC 160. Generally, the MME 162 provides bearer and connectionmanagement. All user Internet protocol (IP) packets are transferredthrough the Serving Gateway 166, which itself is connected to the PDNGateway 172. The PDN Gateway 172 provides UE IP address allocation aswell as other functions. The PDN Gateway 172 and the BM-SC 170 areconnected to the IP Services 176. The IP Services 176 may include theInternet, an intranet, an IP Multimedia Subsystem (IMS), a PS StreamingService, and/or other IP services. The BM-SC 170 may provide functionsfor MBMS user service provisioning and delivery. The BM-SC 170 may serveas an entry point for content provider MBMS transmission, may be used toauthorize and initiate MBMS Bearer Services within a public land mobilenetwork (PLMN), and may be used to schedule MBMS transmissions. The MBMSGateway 168 may be used to distribute MBMS traffic to the base stations102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN)area broadcasting a particular service, and may be responsible forsession management (start/stop) and for collecting eMBMS relatedcharging information.

The core network 190 may include a Access and Mobility ManagementFunction (AMF) 192, other AMFs 193, a Session Management Function (SMF)194, and a User Plane Function (UPF) 195. The AMF 192 may be incommunication with a Unified Data Management (UDM) 196. The AMF 192 isthe control node that processes the signaling between the UEs 104 andthe core network 190. Generally, the AMF 192 provides QoS flow andsession management. All user Internet protocol (IP) packets aretransferred through the UPF 195. The UPF 195 provides UE IP addressallocation as well as other functions. The UPF 195 is connected to theIP Services 197. The IP Services 197 may include the Internet, anintranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service,and/or other IP services.

The base station may include and/or be referred to as a gNB, Node B,eNB, an access point, a base transceiver station, a radio base station,a radio transceiver, a transceiver function, a basic service set (BSS),an extended service set (ESS), a transmit reception point (TRP), or someother suitable terminology. The base station 102 provides an accesspoint to the EPC 160 or core network 190 for a UE 104. Examples of UEs104 include a cellular phone, a smart phone, a session initiationprotocol (SIP) phone, a laptop, a personal digital assistant (PDA), asatellite radio, a global positioning system, a multimedia device, avideo device, a digital audio player (e.g., MP3 player), a camera, agame console, a tablet, a smart device, a wearable device, a vehicle, anelectric meter, a gas pump, a large or small kitchen appliance, ahealthcare device, an implant, a sensor/actuator, a display, or anyother similar functioning device. Some of the UEs 104 may be referred toas IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heartmonitor, etc.). The UE 104 may also be referred to as a station, amobile station, a subscriber station, a mobile unit, a subscriber unit,a wireless unit, a remote unit, a mobile device, a wireless device, awireless communications device, a remote device, a mobile subscriberstation, an access terminal, a mobile terminal, a wireless terminal, aremote terminal, a handset, a user agent, a mobile client, a client, orsome other suitable terminology.

Referring again to FIG. 1 , in certain aspects, a first node (e.g. anIAB node or the UE 104) may include a node multiplexing component 198that is configured to transmit a report to a CU, where the reportincludes at least one multiplexing capability of the first node orincludes at least one multiplexing capability condition for the at leastone multiplexing capability of the first node; receive a semi-staticresource allocation from the CU based on the at least one multiplexingcapability; and communicate with a second node based on the semi-staticresource allocation. The node multiplexing component 198 may also beconfigured to receive, from the CU, one or more resource conditions forusing allocated resources of the semi-static resource allocation, and tocommunicate with the second node further based on the one or moreresource conditions. The node multiplexing component 198 may further beconfigured to transmit a change request to the CU to modify thesemi-static resource allocation. The at least one multiplexingcapability may comprise at least one of SDM or FDM, and the SDM mayinclude at least one of SDM FD or SDM HD. The at least one multiplexingcapability may be with respect to one or more transmission directioncombinations of the first node.

Referring again to FIG. 1 , in other aspects, a CU (e.g. an IAB node orthe base station 102/180) may include a CU multiplexing component 199that is configured to receive a report from a first node, where thereport includes at least one multiplexing capability of the first nodeor includes at least one multiplexing capability condition for the atleast one multiplexing capability of the first node; and transmit to thefirst node a semi-static resource allocation based on the at least onemultiplexing capability for communication of the first node with asecond node. The CU multiplexing component 199 may also be configured totransmit, to the first node, one or more resource conditions for usingallocated resources of the semi-static resource allocation, where thecommunication of the first node with the second node is based on the oneor more resource conditions. The CU multiplexing component 199 mayfurther be configured to receive a change request from the first node tomodify the semi-static resource allocation. The at least onemultiplexing capability may comprise at least one of SDM or FDM, and theSDM may include at least one of SDM FD or SDM HD. The at least onemultiplexing capability may be with respect to one or more transmissiondirection combinations of the first node.

Although the following description may be focused on 5G NR, the conceptsdescribed herein may be applicable to other similar areas, such as LTE,LTE-A, CDMA, GSM, and other wireless technologies.

FIG. 2A is a diagram 200 illustrating an example of a first subframewithin a 5G/NR frame structure. FIG. 2B is a diagram 230 illustrating anexample of DL channels within a 5G/NR subframe. FIG. 2C is a diagram 250illustrating an example of a second subframe within a 5G/NR framestructure. FIG. 2D is a diagram 280 illustrating an example of ULchannels within a 5G/NR subframe. The 5G/NR frame structure may be FDDin which for a particular set of subcarriers (carrier system bandwidth),subframes within the set of subcarriers are dedicated for either DL orUL, or may be TDD in which for a particular set of subcarriers (carriersystem bandwidth), subframes within the set of subcarriers are dedicatedfor both DL and UL. In the examples provided by FIGS. 2A, 2C, the 5G/NRframe structure is assumed to be TDD, with subframe 4 being configuredwith slot format 28 (with mostly DL), where D is DL, U is UL, and X isflexible for use between DL/UL, and subframe 3 being configured withslot format 34 (with mostly UL). While subframes 3, 4 are shown withslot formats 34, 28, respectively, any particular subframe may beconfigured with any of the various available slot formats 0-61. Slotformats 0, 1 are all DL, UL, respectively. Other slot formats 2-61include a mix of DL, UL, and flexible symbols. UEs are configured withthe slot format (dynamically through DL control information (DCI), orsemi-statically/statically through radio resource control (RRC)signaling) through a received slot format indicator (SFI). Note that thedescription infra applies also to a 5G/NR frame structure that is TDD.

Other wireless communication technologies may have a different framestructure and/or different channels. A frame (10 ms) may be divided into10 equally sized subframes (1 ms). Each subframe may include one or moretime slots. Subframes may also include mini-slots, which may include 7,4, or 2 symbols. Each slot may include 7 or 14 symbols, depending on theslot configuration. For slot configuration 0, each slot may include 14symbols, and for slot configuration 1, each slot may include 7 symbols.The symbols on DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. Thesymbols on UL may be CP-OFDM symbols (for high throughput scenarios) ordiscrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (alsoreferred to as single carrier frequency-division multiple access(SC-FDMA) symbols) (for power limited scenarios; limited to a singlestream transmission). The number of slots within a subframe is based onthe slot configuration and the numerology. For slot configuration 0,different numerologies μ 0 to 5 allow for 1, 2, 4, 8, 16, and 32 slots,respectively, per subframe. For slot configuration 1, differentnumerologies 0 to 2 allow for 2, 4, and 8 slots, respectively, persubframe. Accordingly, for slot configuration 0 and numerology p, thereare 14 symbols/slot and 2 slots/subframe. The subcarrier spacing andsymbol length/duration are a function of the numerology. The subcarrierspacing may be equal to 24*15 kHz, where μ is the numerology 0 to 5. Assuch, the numerology p=0 has a subcarrier spacing of 15 kHz and thenumerology p=5 has a subcarrier spacing of 480 kHz. The symbollength/duration is inversely related to the subcarrier spacing. FIGS.2A-2D provide an example of slot configuration 0 with 14 symbols perslot and numerology p=2 with 4 slots per subframe. The slot duration is0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration isapproximately 16.67 s.

A resource grid may be used to represent the frame structure. Each timeslot includes a resource block (RB) (also referred to as physical RBs(PRBs)) that extends 12 consecutive subcarriers. The resource grid isdivided into multiple resource elements (REs). The number of bitscarried by each RE depends on the modulation scheme.

As illustrated in FIG. 2A, some of the REs carry reference (pilot)signals (RS) for the UE. The RS may include demodulation RS (DM-RS)(indicated as Rx for one particular configuration, where 100 x is theport number, but other DM-RS configurations are possible) and channelstate information reference signals (CSI-RS) for channel estimation atthe UE. The RS may also include beam measurement RS (BRS), beamrefinement RS (BRRS), and phase tracking RS (PT-RS).

FIG. 2B illustrates an example of various DL channels within a subframeof a frame. The physical downlink control channel (PDCCH) carries DCIwithin one or more control channel elements (CCEs), each CCE includingnine RE groups (REGs), each REG including four consecutive REs in anOFDM symbol. A primary synchronization signal (PSS) may be within symbol2 of particular subframes of a frame. The PSS is used by a UE 104 todetermine subframe/symbol timing and a physical layer identity. Asecondary synchronization signal (SSS) may be within symbol 4 ofparticular subframes of a frame. The SSS is used by a UE to determine aphysical layer cell identity group number and radio frame timing. Basedon the physical layer identity and the physical layer cell identitygroup number, the UE can determine a physical cell identifier (PCI).Based on the PCI, the UE can determine the locations of theaforementioned DM-RS. The physical broadcast channel (PBCH), whichcarries a master information block (MIB), may be logically grouped withthe PSS and SSS to form a synchronization signal (SS)/PBCH block. TheMIB provides a number of RBs in the system bandwidth and a system framenumber (SFN). The physical downlink shared channel (PDSCH) carries userdata, broadcast system information not transmitted through the PBCH suchas system information blocks (SIBs), and paging messages.

As illustrated in FIG. 2C, some of the REs carry DM-RS (indicated as Rfor one particular configuration, but other DM-RS configurations arepossible) for channel estimation at the base station. The UE maytransmit DM-RS for the physical uplink control channel (PUCCH) and DM-RSfor the physical uplink shared channel (PUSCH). The PUSCH DM-RS may betransmitted in the first one or two symbols of the PUSCH. The PUCCHDM-RS may be transmitted in different configurations depending onwhether short or long PUCCHs are transmitted and depending on theparticular PUCCH format used. The UE may transmit sounding referencesignals (SRS). The SRS may be transmitted in the last symbol of asubframe. The SRS may have a comb structure, and a UE may transmit SRSon one of the combs. The SRS may be used by a base station for channelquality estimation to enable frequency-dependent scheduling on the UL.

FIG. 2D illustrates an example of various UL channels within a subframeof a frame. The PUCCH may be located as indicated in one configuration.The PUCCH carries uplink control information (UCI), such as schedulingrequests, a channel quality indicator (CQI), a precoding matrixindicator (PMI), a rank indicator (RI), and HARQ ACK/NACK feedback. ThePUSCH carries data, and may additionally be used to carry a bufferstatus report (BSR), a power headroom report (PHR), and/or UCI.

FIG. 3 is a block diagram of a base station 310 in communication with aUE 350 in an access network. In the DL, IP packets from the EPC 160 maybe provided to a controller/processor 375. The controller/processor 375implements layer 3 and layer 2 functionality. Layer 3 includes a radioresource control (RRC) layer, and layer 2 includes a service dataadaptation protocol (SDAP) layer, a packet data convergence protocol(PDCP) layer, a radio link control (RLC) layer, and a medium accesscontrol (MAC) layer. The controller/processor 375 provides RRC layerfunctionality associated with broadcasting of system information (e.g.,MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRCconnection establishment, RRC connection modification, and RRCconnection release), inter radio access technology (RAT) mobility, andmeasurement configuration for UE measurement reporting; PDCP layerfunctionality associated with header compression/decompression, security(ciphering, deciphering, integrity protection, integrity verification),and handover support functions; RLC layer functionality associated withthe transfer of upper layer packet data units (PDUs), error correctionthrough ARQ, concatenation, segmentation, and reassembly of RLC servicedata units (SDUs), re-segmentation of RLC data PDUs, and reordering ofRLC data PDUs; and MAC layer functionality associated with mappingbetween logical channels and transport channels, multiplexing of MACSDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs,scheduling information reporting, error correction through HARQ,priority handling, and logical channel prioritization.

The transmit (TX) processor 316 and the receive (RX) processor 370implement layer 1 functionality associated with various signalprocessing functions. Layer 1, which includes a physical (PHY) layer,may include error detection on the transport channels, forward errorcorrection (FEC) coding/decoding of the transport channels,interleaving, rate matching, mapping onto physical channels,modulation/demodulation of physical channels, and MIMO antennaprocessing. The TX processor 316 handles mapping to signalconstellations based on various modulation schemes (e.g., binaryphase-shift keying (BPSK), quadrature phase-shift keying (QPSK),M-phase-shift keying (M-PSK), M-quadrature amplitude modulation(M-QAM)). The coded and modulated symbols may then be split intoparallel streams. Each stream may then be mapped to an OFDM subcarrier,multiplexed with a reference signal (e.g., pilot) in the time and/orfrequency domain, and then combined together using an Inverse FastFourier Transform (IFFT) to produce a physical channel carrying a timedomain OFDM symbol stream. The OFDM stream is spatially precoded toproduce multiple spatial streams. Channel estimates from a channelestimator 374 may be used to determine the coding and modulation scheme,as well as for spatial processing. The channel estimate may be derivedfrom a reference signal and/or channel condition feedback transmitted bythe UE 350. Each spatial stream may then be provided to a differentantenna 320 via a separate transmitter 318TX. Each transmitter 318TX maymodulate an RF carrier with a respective spatial stream fortransmission.

At the UE 350, each receiver 354RX receives a signal through itsrespective antenna 352. Each receiver 354RX recovers informationmodulated onto an RF carrier and provides the information to the receive(RX) processor 356. The TX processor 368 and the RX processor 356implement layer 1 functionality associated with various signalprocessing functions. The RX processor 356 may perform spatialprocessing on the information to recover any spatial streams destinedfor the UE 350. If multiple spatial streams are destined for the UE 350,they may be combined by the RX processor 356 into a single OFDM symbolstream. The RX processor 356 then converts the OFDM symbol stream fromthe time-domain to the frequency domain using a Fast Fourier Transform(FFT). The frequency domain signal comprises a separate OFDM symbolstream for each subcarrier of the OFDM signal. The symbols on eachsubcarrier, and the reference signal, are recovered and demodulated bydetermining the most likely signal constellation points transmitted bythe base station 310. These soft decisions may be based on channelestimates computed by the channel estimator 358. The soft decisions arethen decoded and deinterleaved to recover the data and control signalsthat were originally transmitted by the base station 310 on the physicalchannel. The data and control signals are then provided to thecontroller/processor 359, which implements layer 3 and layer 2functionality.

The controller/processor 359 can be associated with a memory 360 thatstores program codes and data. The memory 360 may be referred to as acomputer-readable medium. In the UL, the controller/processor 359provides demultiplexing between transport and logical channels, packetreassembly, deciphering, header decompression, and control signalprocessing to recover IP packets from the EPC 160. Thecontroller/processor 359 is also responsible for error detection usingan ACK and/or NACK protocol to support HARQ operations.

Similar to the functionality described in connection with the DLtransmission by the base station 310, the controller/processor 359provides RRC layer functionality associated with system information(e.g., MIB, SIBs) acquisition, RRC connections, and measurementreporting; PDCP layer functionality associated with headercompression/decompression, and security (ciphering, deciphering,integrity protection, integrity verification); RLC layer functionalityassociated with the transfer of upper layer PDUs, error correctionthrough ARQ, concatenation, segmentation, and reassembly of RLC SDUs,re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; andMAC layer functionality associated with mapping between logical channelsand transport channels, multiplexing of MAC SDUs onto TBs,demultiplexing of MAC SDUs from TBs, scheduling information reporting,error correction through HARQ, priority handling, and logical channelprioritization.

Channel estimates derived by a channel estimator 358 from a referencesignal or feedback transmitted by the base station 310 may be used bythe TX processor 368 to select the appropriate coding and modulationschemes, and to facilitate spatial processing. The spatial streamsgenerated by the TX processor 368 may be provided to different antenna352 via separate transmitters 354TX. Each transmitter 354TX may modulatean RF carrier with a respective spatial stream for transmission.

The UL transmission is processed at the base station 310 in a mannersimilar to that described in connection with the receiver function atthe UE 350. Each receiver 318RX receives a signal through its respectiveantenna 320. Each receiver 318RX recovers information modulated onto anRF carrier and provides the information to a RX processor 370.

The controller/processor 375 can be associated with a memory 376 thatstores program codes and data. The memory 376 may be referred to as acomputer-readable medium. In the UL, the controller/processor 375provides demultiplexing between transport and logical channels, packetreassembly, deciphering, header decompression, control signal processingto recover IP packets from the UE 350. IP packets from thecontroller/processor 375 may be provided to the EPC 160. Thecontroller/processor 375 is also responsible for error detection usingan ACK and/or NACK protocol to support HARQ operations.

At least one of the TX processor 368, the RX processor 356, and thecontroller/processor 359 may be configured to perform aspects inconnection with node multiplexing component 198 of FIG. 1 .

At least one of the TX processor 316, the RX processor 370, and thecontroller/processor 375 may be configured to perform aspects inconnection with CU multiplexing component 199 of FIG. 1 .

An IAB node may be part of a topological framework of parent and childnodes. For example, an IAB node may include a parent IAB node and one ormore child IAB nodes. Each IAB node may also include two logicalcomponents: a mobile terminal (MT) and a distributed unit (DU). The MTof an IAB node may act as a UE for a parent node, for example, bycommunicating with the parent node over a backhaul (BH) link (e.g.receiving downlink transmissions from the parent node and sending uplinktransmissions to the parent node). The DU of an IAB node may act as abase station (e.g. a gNB, an access point, etc.) for one or more childnodes, for example, by communicating with the child node(s) over anaccess link (e.g. receiving uplink transmissions from the child node(s)and sending downlink transmissions to the parent node(s)).

IAB nodes may generally have half-duplex (HD) capability. Under HD, anIAB node may not transmit data at the same time and frequency that itreceives data. For instance, a MT of the IAB node may not transmituplink communications to a parent node on a BH link at the same time andfrequency that it receives uplink communications from a child node on anaccess link. To address the HD constraints of these IAB nodes, IABcommunication may use time division multiplexing (TDM). For example, inTDM, the IAB nodes may receive and transmit data using orthogonal (e.g.non-overlapping) resources in the time domain.

However, spatial division multiplexing (SDM) and frequency divisionmultiplexing (FDM) may be more efficiently used for IAB communication inmillimeter wave (mmW) frequencies (e.g. FR2 band or above 6 GHz). SDMmay be more efficient than TDM in mmW communications since datatransmissions are typically beamformed through the use of an antennaarray at each IAB node. The beamforming allows for reception of datafrom and transmission of data to other nodes over different beams ororthogonal spatial resources. For example, using SDM, an IAB node thatis HD capable may receive data from parent and child nodes over multiplebeams in a set of time domain resources or slots. Moreover, various IABnodes may have full duplex (FD) capability, which allow the IAB nodes toreceive data from and transmit data to parent and child nodes over oneor more links (e.g. BH or access links) at the same time. Additionallyto SDM, IAB nodes may use FDM to receive data from and transmit data toparent and child nodes over different beams over orthogonally separatedresources in frequency. As a result, IAB nodes may communicate with morespatial efficiency and capacity using SDM (with HD or FD capability) orFDM than when using TDM in mmW frequencies with multiple beams.

FIG. 4 is a diagram illustrating various examples 408, 422, 432 ofcommunication between IAB nodes 402 (e.g. IAB nodes 414, 416, 424, 426,434, 436) using TDM, SDM HD (with each IAB node having HD constraints),and SDM FD (with each node having FD capability), respectively. Each IABnode 402 may include a MT 404 and a DU 406. Each IAB node 416, 426, 436may also include a parent BH link to a parent node (e.g. to IAB node414, 424, 434) and a child link to one or more child nodes 418 (whichmay be other IAB nodes or UEs 408), thereby forming a topologicalstructure as illustrated.

In one aspect, IAB nodes 414, 416 may communicate using TDM asillustrated in example 408. In one example of TDM, the communicationsover a parent BH link and child-links may be time division multiplexedwhere active transmissions or receptions are indicated by thicker linesbetween different nodes and only one link is being used to communicateat a time. A link may be made to multiple child nodes 418, e.g., asillustrated by link 410, or to a single child node 418. For instance,example 412 illustrates an active parent-BH-link with an activeconnection between parent IAB node 414 and child IAB node 416. For theactive parent-BH-link with the active connection between the parent IABnode 414 and the child IAB node 416, the DU 406 of the parent IAB node414 and the MT 404 of the child IAB node 416 are in communication witheach other. Similarly, example 420 illustrates an active child link withan active connection between the child IAB node 416 and the child nodes418 of the child IAB node 416. For the active connection between thechild IAB node 416 and the child nodes 418, the DU 406 of the child IABnode 416 is in communication with the child nodes 418.

In an aspect, TDM may be used when the IAB nodes operate under HDconstraints. Accordingly, in these examples 412, 420, the IAB node 416may not transmit data to the parent IAB node 414 and receive data fromthe child nodes 418 over the child link at the same time, since ahalf-duplex device cannot transmit and receive data on the samefrequency at the same time. Thus, example 412 illustrates IAB nodetransmissions occurring over the parent BH link during a firsttime-resource and example 420 illustrates IAB node transmissionsoccurring over the child link during a second time-resource, where thefirst time-resource and the second time-resource are not overlapping intime. The links in diagram 412 and diagram 420 are thus orthogonalrelative to each other.

In another aspect, more efficient resource utilization and improvedperformance compared to TDM may be realized using SDM (e.g. asillustrated at example 422 for HD and example 432 for FD) and FDM. Forinstance, example 428 illustrates an active reception (RX) link betweena half-duplex child IAB node 426 and a parent IAB node 424 and an activeRX link between the half-duplex child IAB node 426 and child nodes 418.Similarly, example 430 illustrates an active transmission (TX) linkbetween a half-duplex child IAB node 426 and a parent IAB node 424 andan active TX link between the half-duplex child IAB node 426 and childnodes 418. The half-duplex child IAB node 426 may thus receive from ortransmit data to both the parent IAB node 424 and the child nodes 418 byusing SDM. Furthermore, example 432 illustrates an active TX/RX linkbetween a full-duplex child node 436 and a parent IAB node 434 and anactive TX/RX link between the full-duplex child IAB node 436 and childnodes 418. The full-duplex child IAB node 436 may thus receive from andtransmit data to both the parent IAB node 434 and the child nodes 418 byusing SDM. As illustrated, the arrows indicate transmission directionand the thicker lines indicate active transmissions. SDM may be atransmission technique that may be used in MIMO wireless communicationand other communications technologies to transmit independently andseparately encoded data signals through reuse of the spatial dimension.

The multiplexing modes SDM HD and SDM FD may be together referred toherein as SDM (e.g., for mmW frequencies) where an SDM enabled IAB node426, 436 may support half-duplex (e.g. example 422) or full-duplex (e.g.example 432) communication. The SDM enabled IAB node 426, 436 mayfurther support FDM. The SDM enabled IAB node 426, 436 may usebeamforming to implement SDM. The SDM enabled IAB node 426, 436 may havemultiple antenna arrays and/or multiple antennas to create multiplebeams at the same time. Accordingly, at example 428, the SDM enabled IABnode 426 may use one beam that is spatially separated from other beamsfor an active RX link with the parent IAB node 424 and one or more otherbeams for an active RX link with the child nodes 418, as indicated bythe wider lines and arrows. Similarly, at example 430, the SDM enabledIAB node 426 may use one beam that is spatially separated from otherbeams for an active TX link with the parent IAB node 434 and one or moreother beams for an active TX link with the child nodes 418, as indicatedby the wider lines and arrows. The transmissions may be spatiallyorthogonal to each other. For SDM full-duplex, as illustrated at example432, the child IAB node 436 that is capable of SDM full duplex may be intwo-way communication with both the parent IAB node 434 and the childnodes 418 as indicated by the thicker lines and arrows between thedevices. Accordingly, the SDM FD may provide the most flexibility out ofSDM FD, SDM HD, FDM, and TDM.

IAB nodes may also operate using single frequency full duplex (SFFD)communication. In SFFD, the IAB nodes may operate under FD using thesame frequency resources for transmission and reception at a given time,similarly to SDM FD but using a single frequency. SFFD may besingle-user or multi-user. In single-user SFFD, an IAB node maybi-directionally communicate (e.g. receive and transmit data) with asingle node (e.g. a UE or other IAB node). In multi-user SFFD, an IABnode with FD capability may simultaneously communicate over multiplelinks to different nodes (e.g. receive data from one node and transmitdata to another node). Multi-user SFFD may include FD-(DU|MT), FD-DU,FD-MT, or any combination of these scenarios. In FD-(DU|MT). an IAB nodewith FD capability simultaneously communicates over its BH link (e.g.receives data at its MT from a parent node) and child link (e.g.transmits data from its DU to a child node). In FD-DU, the DU of the IABnode has FD capability and communicates with multiple child nodes (e.g.an IAB node or a UE), while the MT is not engaged in any communication(e.g. the DU transmits data to a child node and receives data fromanother child node). In FD-MT, the DU is not active, while the MT isactively communicating using FD with multiple parent nodes (e.g. the MTreceives data from a parent node and transmits data to another parentnode). Any combination of the above scenarios is also possible in SFFD.Examples of SFFD are described below with respect to FIG. 5 .

FIG. 5 is a diagram 500 illustrating various SFFD scenarios. The SFFDscenarios may be combined. In a first SFFD scenario 502, a single-userSFFD may be used for IAB node communication. For example, the first SFFDscenario 502 may include an IAB specific scenario with an IAB node 501communicating with another IAB node using single frequency full-duplex.In another example, the first SFFD scenario 502 may include a non-IABspecific scenario with an IAB node 503 communicating with a UE usingsingle frequency full-duplex.

In a second SFFD scenario 504, full-duplex distributed unit/mobileterminal (FD-(DU|MT)) may be used for IAB node communication. Forexample, an IAB node 505 may communicate with a parent IAB node and achild IAB node using single frequency full-duplex over a parent BH linkand a child BH link, respectively. For instance, a MT of IAB node 505may receive data from a DU of a parent IAB node at the same time that aDU of IAB node 505 may transmit data to an MT of a child IAB node, andvice-versa. In another example, an IAB node 506 may communicate with aparent IAB node and a UE using SFFD. For instance, a MT of IAB node 506may receive data from a DU of a parent IAB node at the same time that aDU of IAB node 506 may transmit data to a UE, and vice-versa. The secondSFFD scenario thus provides SDM FD communication over a parent BH linkand a child access link (e.g. with a UE).

In a third SFFD scenario 508, a full-duplex distributed unit (FD-DU) maybe used for IAB node communication. As illustrated, three examples ofthe (FD-DU) scenario may be possible. In one example, an IAB node 510with FD-DU may communicate with two IAB nodes 512 over two child links.In another example, the IAB node 510 may communicate with two UEs 514over two child links. In a further example, the IAB node 510 maycommunicate with child nodes 516 (e.g. one IAB node and one UE) overdifferent child links.

In a fourth SFFD scenario 518, a full-duplex mobile terminal (FD-MT) maybe used for IAB node communication. An IAB node 520 with FD-MT mayinclude a MT that has full duplex capability and thus be able tosimultaneously communicate with two other parent IAB nodes. Forinstance, as illustrated in FIG. 5 , the IAB node 520 may simultaneouslytransmit data to one parent IAB node and receive data from anotherparent IAB node.

The SDM capability of an IAB node (either HD or FD as illustrated inFIG. 4 , including SFFD as illustrated in FIG. 5 ) may be unconditionalor conditional. When an IAB node has conditional SDM capability, the IABnode may communicate using SDM subject to certain constraints orconfigurations. Various examples of these constraints or conditions aredescribed below.

In one example, SDM capability may be beam-dependent, where an IAB nodemay be configured to use SDM on certain subsets of beams but not allbeams. For instance, an IAB node may be configured with a set of beams1, 2, and 3 for communication with other nodes. If beams 1 and 2 aresufficiently spatially separated for SDM (e.g. they are far enough apartto not interfere with each other), but beams 1 and 3 are notsufficiently spatially separated for SDM (e.g. they are too closetogether and may possibly interfere with each other), the IAB node mayuse SDM when communicating using beams 1 and 2 but not when using beams1 and 3.

In another example, SDM capability may be link-budget (LB) dependent,where an IAB node may be configured to use SDM based on a targetsignal-to-noise (SNR) over a given link (e.g. a parent BH link or achild access link). For instance, use of SDM may result in lower SNR dueto the presence of multiple data streams (which each may be subject tonoise). Therefore, if a higher LB is required for a given link (e.g. thetarget SNR is high, such as at least 30 dB), the IAB node may not useSDM in order to allow the node to achieve the expected LB over thatlink. On the other hand, if a lower LB is sufficient for a given link,the IAB node may use SDM over that link.

In a further example, SDM capability may be link or beam-pair specific,where an IAB node may be configured to use SDM over specific pairs ofbeams or links (e.g. beams over a parent BH link and a child accesslink, or over two child links). For example, an IAB node may includepairs of links to multiple nodes (e.g. parent and child nodes, asillustrated in FIGS. 4 and 5 ), and the IAB node may communicate usingSDM over a subset of the link pairs. For instance, an IAB node thatincludes one parent and two children may have multiple link pairs (e.g.one pair may include a parent BH link and a first child access link,another pair may include the parent BH link and a second child accesslink, and a further pair may include both child access links), and theIAB node may be configured to communicate using SDM over one or more,but not all, of the link pairs. As an example, the IAB node may beconfigured to multiplex receptions from the parent node andtransmissions to the first child node, but may not multiplextransmissions to the parent and receptions from the second child node.Other examples of beam-pair/link constraints are possible.

In an additional example, SDM capability may be physical-channelspecific, where the IAB node may communicate using SDM over certainphysical channels but not others. For instance, a control channel mayhave lower LB requirements than a data channel, and thus the IAB nodemay communicate using SDM over the control channel but not over the datachannel. Similarly, other physical channels may have different LBrequirements and thus impact SDM capability of the IAB node.

Thus, an IAB node may have conditional SDM capability as describedaccording to the various example conditions above. Alternatively, an IABnode may have unconditional SDM capability. When an IAB node hasunconditional SDM capability, the IAB node may communicate with othernodes (e.g. parent nodes or child nodes) over respective linksregardless of the beams being used for transmission or reception, linkbudget requirements, the links or beam pairs available to bemultiplexed, the physical channels used to carry the communications, orother conditions. However, absolute, unconditional SDM capability maynot be feasible in certain circumstances. For instance, beams generallyrequire sufficient spatial separation to operate properly, or large linkbudgets may be expected over a particular channel, thereby imposingconstraints on SDM. Accordingly, an IAB node with unconditional SDMcapability may effectively be constrained to communicate using SDM basedon its topology with respect to other nodes. For instance, in atopological structure where an IAB node has a parent node and one childnode, the IAB node may assume that the parent node and child node aresufficiently separated. Therefore, the IAB node may be configured tocommunicate using SDM in this topological structure, but not in othertopological structures where sufficient separation may not be assumed(e.g. where the IAB node includes several child nodes that may be closetogether). Additionally, a parent IAB node (or a CU) may signal a childIAB node as having conditional or unconditional SDM capability based onone or more bits, e.g. one bit indicating whether conditional orunconditional, and other bits indicating, if conditional, the appliedconstraints (e.g. the examples described above).

FIG. 6 is a diagram 600 illustrating SDM (half-duplex or full-duplex)resource management. The SDM(FD/HD) capability of a node may beconditional. For example, the SDM(FD/HD) capability of a node may befeasible only for some configurations. For instance, the SDM(FD/HD)capability of a node may depend on link budget (i.e. be LB-dependent).For example, SDM may not be used when a particular SNR cannot be metwhile using SDM. Accordingly, links that may require a high SNR, e.g.,30 dB, may not be capable of SDM in some instances, while also achievingthe required link budget.

The SDM(FD/HD) capability being LB-dependent may lead to(link/beam-pair)-specific and/or physical-channel-specific capabilities.For example, some channels may be capable of SDM and other channels maynot be capable of SDM due to LB requirements. For example, a controlchannel may be capable of SDM, while a data channel may not be capableof SDM. Alternatively, a control channel may not be capable of SDM,while a data channel may be capable of SDM.

In another aspect, SDM capability may be beam dependent. For example,beam 1 of an IAB node and beam 3 of the IAB node may be full-duplexcapable, while beam 2 of the IAB node may not be full-duplex capable. Inthe examples 602, 604 illustrated in diagram 600, a MT's communication(e.g., over a parent BH link) may be SDM (FD/HD) only with a subset of aDU's communications. For instance, in one example 602, with three IABnodes 605, a parent BH link and a child access link may be provided. Inanother example 604, with two IAB nodes 605 and a UE, a parent BH linkand a child access link may similarly be provided. In these examples,SDM FD may only be provided for some configurations (e.g. beams), asindicated by the dotted lines for some of the transmissions.

In other cases, a node may have unconditional SDM capability.Accordingly, such a node may be capable of SDM for all possible cases.For instance, the node may not be SDM restricted due to link budget,antenna/beam configurations, or other factors. For example, SDM(FD/HD)may be performed using any set of beams and may achieve any link-budget(LB). Some devices may not be capable of absolutely unconditional SDM,however, but may be constrained based on topological structure. For oneexample scenario, unconditional SDM may be the case when, e.g., the MTand DU have separate components, each having different spatialcoverages. Where the MT and DU of an IAB node may have separatecomponents each having different spatial coverages, such configurationmay lead to unconditional capability of SDM(HD/FD) for the device's BHand child links.

IAB nodes may be in communication with a central unit (CU). The CUresides at an IAB donor node, which is the node at the head (or root) ofthe topology of IAB nodes. The CU may include a wired backhaul link(e.g. a fiber connection) to the core network (e.g. core network 190 inFIG. 1 ). The CU interfaces with the various IAB nodes, e.g., to provideresources for wireless communication between various parent and childnodes. For example, referring to the examples of FIG. 6 , the parent IABnodes of IAB nodes 605 may each be an IAB donor 606 that is connected toa core network through a wired connection (e.g. fiber cable). The CU maybe located at the IAB donor 606. The IAB donor may be at the head of achain or tree of other IAB nodes and/or UEs, as illustrated for examplein FIG. 6 .

The IAB nodes may coordinate with the CU to enable the CU to moreefficiently operate the network and semi-statically allocate and manageresources for the IAB nodes. For example, with some coordination or fullcoordination between an IAB-node and the CU, more efficient SDM(FD/HD)operation and better resource utilization of IAB nodes may be achieved.Furthermore, local coordination between a child IAB-node and a parentIAB node, which is separate from coordination between the child IAB-nodeand the CU (typically located multiple hops away), may also allow formore efficient SDM(FD/HD) operation and better resource utilization.

FIG. 7 is a diagram 700 illustrating an example of an IAB resourcemanagement framework. Optional aspects are illustrated in dashed lines.The diagram 700 includes a parent node 702, a child node 704, and a CU706. The parent node 702 may correspond to parent IAB node 414, 424, 434of FIG. 4 (and/or IAB nodes 501, 503, 505, 506, 510, 605 of FIGS. 5 and6 ), for example, and the child node 704 may correspond to child IABnode 416, 426, 436 of FIG. 4 (and/or IAB nodes 505, 506, 512, 520, 605of FIGS. 5 and 6 ), for example. The CU 706 may correspond to the CU inIAB donor 606 of FIG. 6 , for example. The parent node 702 and the childnode 704 may be connected to the CU 706. The connection between theparent node 702, the child node 704, and the CU 706 may be over the air(OTA). Furthermore, the connection may be over one or more hops.

The CU 706 may be the decision maker for the system that includes theparent node 702 and the child node 704. The parent node 702 may transmita report 708 to the CU 706. Similarly, the child node 704 may transmit areport 710 to the CU 706. The report 708, 710 may be received by the CUdirectly or indirectly over multiple hops, as discussed. Reports 708,710 may include one or more of beam/channel quality measurements (e.g.performed by parent node 702, child node 704, or children of child node704), cross-link interference (CLI) measurements (e.g. performed byparent node 702, by child node 704, or by children of child node 704),radio resource management (RRM) measurements (e.g. for discovering newneighboring nodes to parent node 702 and/or child node 704), and/ortraffic or load information.

Based on the report 708 and/or 710, the CU 706 may transmit asemi-static resource allocation 712 to the parent node 702 and/or childnode 704. For example, where TDM is used for JAB node communication asdescribed above in example 408 of FIG. 4 , the semi-static resourceallocation 712 may include information related to the allocation oftime-domain resources, e.g., a set of time domain resources to be usedfor TDM.

The information related to the allocation of time-domain resources mayinclude information on hard resources, soft resources, and/or resourcesthat are not-available. Not-available resources may be those which theCU 706 indicates the parent node 702 may not use to communicate withchild node 704. Accordingly, these resources may not be available forTDM, nor for a given frequency at a particular time. If a resource isconfigured as not available, the DU of the parent node or the child nodecannot assume it can use the resource.

A hard resource may be a resource that the CU 706 indicates is availablefor a parent node 702 to communicate with a child node 704, or for thechild node to communicate with its own children, with no conditions(e.g. the allocated resources may be flexible for use by parent nodeand/or child node). In the case of hard DU resources, the DU of theparent node or the child node can assume it can use the resourceregardless of the MT's configuration. However, exceptions may arise forspecific signals/channels to be transmitted or received by the MT in thesame resource (e.g. SS/PBCH blocks, SI reception, RACH).

A soft resource may be a resource that could be used by an IAB node(e.g. child node 704), and/or could become available for that IAB nodeto use, based on a decision of the parent node 702. For instance, thesoft resource may be released (and later reclaimed) by the parent node702 during local coordination between the parent node and the child node704 (e.g. some interaction or signaling). As an example, if the CU 706allocates slot N as available for child node 704 as a soft resource, thechild node 704 may not use that resource to communicate with itschildren at slot N unless the parent node releases that resource to thechild.

In the case of soft DU resources, if the soft resource is indicated asavailable, the DU of the parent node or the child node can assume it canuse the resource. Alternatively, if the soft resource is not indicatedas available, the DU cannot assume it can use the resource. The use ofsoft resources may at least correspond to transmission/reception ofspecific signals and channels (e.g. PDSCH/PUSCH) at the DU. For example,soft resources may be used for cell-specific signals (e.g. SS/PBCHblocks, SI reception, RACH) signals and channels which may potentiallybe transmitted or received at the DU. Additionally, the availability ofsoft resources at the parent node or child node may be explicitly orimplicitly indicated. For example, in case of implicit indication of DUsoft resource availability, the IAB node may know that the DU resourcecan be used without impacting the MT's ability to transmit/receiveaccording to its configuration and scheduling based on indirect means.Moreover, explicit indication that a resource is available may be basedon DCI indication.

The information related to the allocation of time-domain resources mayalso include information on allowed uses of the resources, such as atransmission direction of the resources. For instance, the CU 706 mayindicate a hard or soft resource as available only for downlink (DL)communications, available only for uplink (UL) communications, or withflexible availability, all of which may respectively be indicated asD/U/F. Flexible availability may indicate that the resources areavailable for both DL and for UL, based on a decision of an IAB node.Accordingly, using the resources, interaction and signaling may occurbetween the parent node 702 and the child node 704. The resources may beused for communications from the parent node 702 to the child node 704,from the child node 704 to the parent node 702, from the parent node 702to other children, and/or from the child node 704 to other nodes,including children.

Accordingly, when the semi-static resource allocation 712 for child node704 includes soft resources, at 714, the parent node 714 may releaseand/or reclaim the child node's 704 soft resources. For example, thechild node's 704 soft resources may be released by the parent node 714so that the child node's 704 soft resources may be used by the childnode 704. Alternatively, the child node's 704 soft resources may bereclaimed (e.g., after previously being released to the child node 704)by the parent node 714 so that the child node's 704 soft resources maynot be used by the child node 704.

At 716, the parent node 702, the child node 704, and other child nodes(not shown) may establish communication links over the allocated timedomain resources (hard or soft resources). Accordingly, the parent node702, the child node 704, and the other nodes may communicate over theestablished communication links in their topology based on thesemi-static resource allocation 712.

FIG. 8 is a diagram 800 illustrating an example of CU-DU coordinationfor SDM full-duplex and SDM half-duplex operation. Optional aspects areillustrated in dashed lines. The diagram 800 includes a parent node 802,a child node 804, and a CU 806. Parent node 802, child node 804, and CU806 may correspond to parent node 702, child node 704, and CU 706 ofFIG. 7 , respectively, for example. The parent node 802 and the childnode 804 may be connected to the CU 806. The connections between theparent node 802, the child node 804, and the CU 806 may be OTA.Furthermore, the connections may be over one or more hops.

At 805, to enable efficient SDM operation, the child node 804 mayperform local interference measurements. In one example, for SDM (FD)operation, the child node may measure self-interference between its owntransmission and reception beams. In a device, such as the child node804, a transmission of a signal by the child node 804 over atransmission (Tx) beam may collide with a received signal by the childnode 804 over a reception (Rx) beam. Such self-interference may preventthe child node from effectively performing SDM with full-duplexcapability. Accordingly, the child node 804 may measureself-interference for different combinations of TX/RX beams.

In an aspect, self-interference may include clutter echo. For example, atransmission from the child node 804 may be reflected off of an objectand be received by the child node 804. Such clutter echo may interferewith signals that the child node 804 is attempting to receive andprocess. Accordingly, when performing self-interference measurements,the child node may consider the reflected signals that may causeinterference. For instance, as a part of the local measurements, thechild node 804 may modify its corresponding TX/RX beanformingconfiguration (e.g. to implement beam nulling on beams withself-interference). Thus, the child node may determine not to use beamswith measured self-interference for SDM (FD).

In another example, for SDM (HD) operation, the child node 804 maymeasure cross-beam interference, in which a transmission (or reception)over one beam of the child node may interfere with a transmission (orreception) over another beam of the child node. For example, the childnode 804 may receive data from parent node 802 over beam 1 (the parentBH link) and simultaneously receive data from its own child nodes overbeam 2 (the child link). Accordingly, while receiving from the parentnode 802 on beam 1, the child node 804 may check the received power onbeam 2. If the received power on beam 2 indicates cross-beaminterference from the reception on beam 1, the child node may determinenot to use these beams for SDM (HD). In another example, if the childnode receives data from its own children over beam 1 and simultaneouslyreceives data from parent node 802 over beam 2, then while schedulingand receiving over the child-link using beam 1, the child node 904 maymeasure received power on beam 2 and similarly determine not to usethese beams for SDM (HD) if cross-beam interference is identified.

As in the example of FIG. 7 , the parent node 802 may transmit a report808 to the CU 806. Moreover, after performing the local interferencemeasurements at 805, the child node 804 may similarly transmit a report810 to the CU 806. The report 808, 810 may be received by the CU 806directly or indirectly over multiple hops, as discussed. One or more ofthe reports 808, 810 may include one or more of beam/channel qualitymeasurements, cross-link interference (CLI) measurements, radio resourcemanagement (RRM) measurements, and/or traffic/load report, as describedabove with respect to FIG. 7 .

Additionally, the report 810 from the child node 804 to the CU 806(directly or indirectly transmitted to the CU, e.g. through parent node802) may include the results of the local interference measurements. Inone example, the report 810 may indicate to the CU the self-interferenceand cross-beam interference measurements. In another example, ratherthan sharing a full measurement report with the CU, the child node maydetermine from the measurement results whether it has FD or HDcapability for SDM and whether the SDM capability is unconditional orconditional (with conditions as described above), and indicate thatcapability or conditions to the CU. Moreover, if the SDM capability isconditional, the report 810 to the CU may include the SDM FD or SDM HDconditions of the child node (e.g. beams that may be used for SDM, linkbudget requirements, the links or beam pairs available for SDM, and/orthe physical channels available for SDM). When the CU 806 receives thereport 810 from the child node 804, the CU may transmit to the parentnode 802 an indication of the capability or conditions of the childnode. The report 808 from the parent node 802 may similarly include SDMcapability and/or conditions of the parent node, and the CU 806 maysimilarly transmit to the child node 804 an indication of the capabilityor conditions of the parent node.

For example, the report 808, 810 may include the SDM FD or SDM HDcapability of a particular node. The report 808, 810 may indicate themultiplexing capability of the parent node or the child node for thecase of no-TDM (e.g. SDM or FDM) between the IAB MT and the IAB DU ofthat node with respect to each transmission-direction combination (perMT component carrier (CC)/DU cell pair). For instance, the report mayindicate SDM or FDM capability of the parent node or child node withrespect to transmission-direction combinations including MT-TX/DU-TX(the MT transmits while the DU transmits), MT-TX/DU-RX (the MT transmitswhile the DU receives), MT-RX/DU-TX (the MT receives while the DUtransmits), and MT-RX/DU-RX (the MT receives while the DU receives).Moreover, the report 810 from the child node 804 may indicate, to eitherthe donor CU or the parent node 802, the multiplexing capability betweenMT and DU (TDM required, TDM not required) of an IAB node for any {MTCC, DU cell} pair. Furthermore, the report 808, 810 may indicateconditions such as which pairs of beams or pairs of links may be usedfor SDM. The report 810 may also indicate when there may be anylimitation on the link-budget, such as a maximum TX power or a maximumRX power for a given link.

As in FIG. 7 , the CU 806 may transmit a semi-static resource allocation812 to the parent node 802 and/or child node 804. The semi-staticresource allocation 812 may include information related to theallocation of time-domain resources. Thus, TDM, SDM half-duplex, and/orSDM full-duplex operation may be adopted over different sets oftime-domain resources between parent and child nodes through theconfiguration of semi-static resource allocation 812. The informationrelated to the allocation of time-domain resources may includeinformation on hard resources, soft resources, and/or resources that arenot-available. The information related to the allocation of time-domainresources may also include information on allowed uses of the resources,such as availability for DL, availability for UL, or flexibleavailability (D/U/F). The resources may be used for communications fromthe parent node 802 to the child node 804, from the child node 804 tothe parent node 802, from the parent node 802 to other children, and/orfrom the child node 804 to other nodes, including children.

The CU 806 may also transmit conditions 814 to one or more of the parentnode 802 and/or the child node 804 for use of the resources ofsemi-static resource allocation 812. For instance, the conditions mayindicate that the resources are available for the parent node 802 and/orchild node 804 to use SDM for a subset of beams, links, physicalchannels, etc. The conditions 814 may also include the conditionsreported by the child node to the CU 806 (or indirectly to parent node802) in report 810. The conditions 814 may be included in thesemi-static resource allocation 812, or the conditions 814 may betransmitted separately from the semi-static resource allocation 812 asillustrated in FIG. 8 .

The conditions 814 may provide additional control over how the resourcesin semi-static resource allocation 812 are used by the one or more ofthe parent node 802 and/or the child node 804. For example, the CU 806may use the conditions 814 to indicate whether a set of allocatedtime-domain resources may be used unconditionally or not for SDMFull-duplex or Half-duplex operation. Conditions 814 may include thedirectional conditions (D/U/F) described above, as well as additionalconditions for conditional use. For example, in a case of conditionaluse, the CU 806 may further indicate as conditions 814 variousconstraints such as those on modulation coding scheme (MCS, e.g. themaximum MCS used over the allocated resources), transmit (Tx) power(e.g. the maximum Tx power that may be used), receive (Rx) power (e.g.the maximum Rx power that may be used), TX/RX beam(s) that may be used(e.g. the subset of beams or beam pairs/links that may be used),frequency-domain resources (e.g. the limited RBs that may be used overan indicated set of time domain resources in the semi-static resourceallocation), reference signal configuration/resources (e.g. the specifictones or resources that DMRS or another reference signal may betransmitted), and timing reference (e.g. the Tx/Rx timing to be used foralignment with other simultaneous communications).

Accordingly, the conditions 814 may set on one or more of the MCS,transmit power, receive power, TX/RX beam, frequency-domain resources,reference signal configuration/resources, timing reference, or otherconditions for the parent node 802 and/or the child node 804. Forexample, the MCS may be used to indicate a cap for the MCS. In anaspect, the transmit power or receive power may be capped. In an aspect,the TX/RX beam used may be limited. In an aspect, the frequency-domainresources may be limited to a given sets of RBs. In an aspect, aparticular reference signal configuration/resources may need to beadopted. In an aspect, timing reference may be used to adjust receivetiming, e.g., to align on other communications.

In an aspect, the conditions 814 to use the resources may identify theexpected behavior of the parent node 802 regarding the resources. Forexample, when resources are labeled as hard for both the parent node 802and the child node 804, this indicates that the resources may be used byeither the parent node 802 or the child node 804 without limitation.Accordingly, in some cases scheduling conflicts may occur because boththe parent node 802 and the child node 804 have a same set of resourcesindicated as hard resources. For instance, if the child node 804 has HDcapability and determines to transmit to its own child nodes using itshard resources at the same time the parent node 802 determines totransmit to child node 804 using its hard resources, a collision mayoccur. Accordingly, determinations (e.g. conflict resolutions) may bemade about whether the parent node 802 should yield using theseresources to the child node 804 and/or whether the parent node 802 mayuse these resources subject to certain constraints (e.g. complying withthe schedule of the child's node).

For example, inter-IAB node conflict resolution may be supported by oneor more of the following options: the parent node is aware of all of theDU resource configurations (D/U/F/hard [H]/soft [S]/not-available [NA])of its child IAB node DUs, or the parent node may be aware of a subsetof the DU resource configurations (D/U/F/H/S/NA) of its child IAB nodeDUs. The indication of the child DU resources at the parent node may bevia explicit means (e.g. F1-AP signaling) or implicit means (e.g. basedon child MT configuration). Thus, if parent node 802 is made aware ofchild node 804's resource configurations or is aware of a subset ofthese resource configurations (via explicit signaling, such as insemi-static resource allocation 812, or based on the child node's MTconfiguration), the parent node may prevent conflicts by yielding hardresources centrally and semi-statically controlled by the CU 806 (sincethe parent node may not expect the child's MT to be available forcommunication within these resources), or by releasing/reclaiming softresources locally and dynamically controlled by the parent node's DU.Alternatively, to prevent such conflicts and avoid conflict resolution,the semi-static resource allocation 812 may include orthogonal resourcesfor the parent node and child node to use over TDM, thereby addressinghalf duplex constraints of child nodes.

However, if a child node has SDM (half-duplex or full duplex)capability, the child node may be able to communicate with the parentand/or its own children at the same time, and the above conflictresolution rules may be moot. Therefore, to provide more efficientoperation than TDM, the semi-static resource allocation may include asame set of resources for both the parent node 802 and the child node804 for communicating using SDM. For example, a parent node 802/childnode 804 pair having a hard/hard (HARD∥HARD) resource allocation (e.g.,a hard resource allocation to both a parent node and a child node) maynot cause a conflict when the child node has HD or FD capability andcommunicates with the parent node using SDM. Thus, for more efficientoperation, conflict resolution may be unnecessary in such cases where aconflict may not occur for a device with SDM half-duplex or full-duplexcapability.

Accordingly, the semi-static resource allocation 812 and/or conditions814 may identify an expected behavior of the parent node 802 as analternative to the aforementioned conflict resolution rules. Forexample, if the resource allocation for a same set of resources is(HARD∥HARD), rather than yielding the resources to the child node 804 asdescribed above, the conditions 814 may indicate to the parent node 802an expected behavior not to yield the resources for use by its childrenwhen the child node 804 has HD or FD capability (since the child nodemay simultaneously communicate with its own child nodes and parent nodeand no conflict will arise).

Similarly, the conditions to use resources may identify the expectedbehavior of parent node 802 regarding a child node's 804 soft resources,for example, whether the parent node may conditionally release theresources, e.g., whether the parent node may still use the releasedresources to communicate with the child in an SDM HD/FD manner. Whenresources are labeled soft, this indicates that the parent node 802 mayuse the resources until it releases them to the child node 804, afterwhich the parent node may not generally use the resources to communicatewith the child node. This prevents conflicts from occurring when thechild node is TDM HD capable (e.g. when the child node is communicatingover different resources than the parent node). However, although suchconflicts may not occur during TDM, when the child node is SDM HD or FDcapable, more efficient operation may occur using SDM. For example, noconflicts may arise when the parent node 802 communicates usingreleased, soft resources with a child node 804 that is HD or FD capable,since the child node 804 may communicate with its own child nodes at thesame time that it communicates with the parent node 802. Therefore, theconditions 814 may indicate to the parent node an expected behavior notto refrain from using released soft resources when communicating withthe child node. Accordingly, the resources are conditionally releasedsince the parent node may continue to use the released resources.

The conditions to use resources may also identify the expected behaviorof the child node 804 regarding the child node's 804 soft resources, forexample, the condition may identify whether the child may conditionallyuse the soft resources in SDM HD or FD manner when not explicitly bannedby the parent node 802. When resources are labeled soft, this indicatesthat the resources may generally be used by the child node when releasedby the parent node, and that the resources may not generally be used bythe child node when reclaimed by the parent node. As discussed above,this prevents conflicts from occurring when the child node is TDM HDcapable; however, when the child node is SDM HD or FD capable, moreefficient operation may occur using SDM since the child node 804 maycommunicate with its own child nodes at the same time that itcommunicates with the parent node 802. Therefore, the conditions 814 mayindicate to the child node 804 an expected behavior not to refrain fromusing unreleased (or reclaimed) soft resources when communicating withits own child nodes. Accordingly, the child node 804 may conditionallyuse soft resources to communicate with its children even when the softresources are not released or reclaimed, absent an explicit ban of childresource usage by the parent node 802. Communication between parentnodes 802 and child nodes 804 may thus allow conflict rules to beavoided based on capabilities of the parent nodes 802 and child nodes804.

At any given time, a system configuration (e.g. the quality of thechannel, mobility of the system, etc.) may change due to the dynamicnature of wireless communication systems. For example, the child node804 and parent node 802 may drop some beams in favor of other beams forcommunication, or link budgets (e.g. target SNRs) may change overvarious parent or child links. For instance, at 820 and 822,respectively, the parent node and/or child node may modify theirtransmission or reception beams (e.g. based on local interferencemeasurements performed at 805). Whenever such changes occur, the SDMcapability of the child node and/or parent node may correspondingly alsochange. For example, even though SDM between two old beams may have beenfeasible, SDM between two new beams may not be feasible. As a result,the semi-static resource allocation 812 may no longer be efficient forSDM operation in such cases, and a new semi-static resource allocationmay be configured. Alternatively, the reverse may be true; for example,even though SDM between two old beams was not feasible, SDM between twonew beams may now be feasible. As a result, a more efficient semi-staticresource allocation 812 may be configured to enable SDM operation insuch cases.

To report such changes to the CU 806 and request a new semi-staticresource allocation accordingly, the child node 804 may send a changerequest 816 to the CU 806. Similarly, the parent node 802 may send achange request 818 to the CU 806. The change requests 816, 818 mayindicate a new configuration of the parent or child node (e.g. changedbeams, link budget, etc.). For instance, the change requests 816, 818may indicate that one or more beams (or beam pairs) over a parent BHlink and/or child access link has changed, or that a link budget overone or more physical channels has changed. The change requests 816, 818may also request the CU 806 to provide a new resource allocation (RA)based on the new configuration. For example, the change request mayrequest the CU to provide a new RA which may enable SDM (FD/HD)operation over the new beams or links of the parent or child nodeindicated in the change request, or to provide a new RA that may accountfor changes in beams or link budget indicated in the change request whenSDM(FD/HD) between two current links is no longer feasible. Thus,resources may be re-allocated by the CU in response to change requests816 and/or 818.

Thus, based on the coordination between the parent node 802, child node804, and CU 806 discussed above, the parent node and child node maycommunicate using the semi-static resource allocations 812 not onlybased on TDM but also more efficiently using SDM (HD or FD). Forexample, at 824, FD communication may occur between parent node 802 andchild node 804 over a (HARD∥HARD) link, e.g. when a time-domain resourceis configured as hard for both a parent node and a child node by the CU806. If the child node 804 has the capability of SDM full-duplex underspecified conditions (e.g. conditions 814), once the conditions are met,both the parent node and the child node may use the hard resources forcommunication simultaneously in an SDM full-duplex manner. In anotherexample, at 826, FD communication may occur over a (Soft+∥Hard) link.For example, the CU 806 may configure a time-domain resource as soft forthe parent node and as hard for the child node. Furthermore, the softresource at the parent node may be indicated “soft+”, in which the softresource is available for the parent node when released by the parentnode's own parent node (e.g., a “grand-parent” node). Thus, the softresource when released by a grandparent node may be used in the same wayas a hard resource by the parent node. In this case, the parent andchild nodes may have (Soft+∥Hard) resource alignment, which may besimilar to the (Hard∥Hard) resource alignment in the above example.

FIG. 9 is a diagram 900 illustrating an example of full-duplex operationwith CU-DU coordination based on the aspects described above withrespect to FIG. 8 . The diagram includes a parent node 902 (e.g. parentnode 802), a parent-link 904, a child node 906 (e.g. child node 804),child-links 908, and connected devices 910 (e.g. JAB nodes and/or UEs).In one example of coordination between the child node 906 and a CU (e.g.CU 806), for FD over hard resources, the CU may become aware ofchild-links 908 that may use FD with a parent-link 904. For example, thechild node 906 and/or parent node 902 may send a report (e.g. report808, 810 of FIG. 8 ) indicating child links 908 are SDM FD capable withparent link 904. While this example assumes that the report indicatesall child links 908 are SDM FD capable with parent link 904, the reportmay alternatively indicate that a subset of child links may be SDM FDcapable (e.g. one or more of the child links 908). Based on thereport(s), in this example, the CU may allocate hard resources to boththe parent node 902 and the child node 906 (e.g. in semi-static resourceallocation 812 of FIG. 8 ). Moreover, the CU may schedule variousRRC-configured/cell-specific communications (e.g., CORESET, systeminformation, RACH information, synchronization signals, etc.) withinthese hard resources when the child node 906 has FD capability.Accordingly, the child node 906 may use FD with SDM to communicate withboth the devices 910 and the parent node 902.

In one aspect, the CU may provide an expected behavior to the parentnode 902. For example, the expected behavior may indicate to the parentnode 902 not to yield within these resources to the child node 906, asdiscussed above, since the child node 906 has FD capability. In a firstaspect, the parent node 902 may not coordinate with the child node 906to determine the resource configuration of the child node's 906 DU (e.g.as having FD capability), and therefore the parent node 902 may blindlyattempt to use the resources when communicating with the child node 906(without additional signaling for expected parent behavior).Alternatively, in a second aspect, the parent node 902 may coordinatewith the child node to determine the resource configuration of the childnode's 906 DU (e.g. as having FD capability), and the CU may notify theparent node 906 an expected behavior not to yield to the child node 906on the resources (or a subset of the resources).

Alternatively, in another aspect, there may not be coordination betweenthe child node 906 and the CU. For example, in some cases the child nodemay not provide a report to the CU including its FD capability orconditions (e.g., report 810), and thus the CU may not be able tocoordinate efficiently, determine the FD capability of the child nodeand/or provide efficient resource allocation to the child node.Therefore, the CU may assume in such cases that the child node has HDcapability, and may thus attempt to guarantee performance by allocatingsome exclusively hard resources (e.g. non-orthogonal resources) to thechild links 908 for TDM usage to prevent conflicts and degradedperformance.

In a further aspect, the CU may allocate hard resources to both theparent node 902 and the child node 906 for opportunistic FDcommunication in a case when no coordination between the child node 906and the parent node 902 is available. Moreover, the CU may allocate hardresources to both the parent node 902 and the child node 906 forefficient FD in a case when local coordination between the child nodeand the parent node is available.

In an additional aspect, the CU may allocate soft resources to the childnode 906. In such case, when the CU is aware or partially aware of theFD capability of the child node 906 (e.g. based on a report by theparent node 902 or the child node 906), the CU may more efficientlyallocate soft resources for the child node to communicate with itschildren over the child-links 908. There may also be local coordinationbetween the child node 906 and the parent node 902 (e.g., the child nodemay request the parent node 902 to conditionally release some softresources to enable FD communication of the child node 906).

FIG. 10 is a flowchart 1000 of a method of wireless communication. Themethod may be performed by a first node, such as an IAB node or UE(e.g., the UE 104, 350, 514, the IAB node 402, 414, 416, 424, 426, 434,436, 501, 503, 506, 506, 510, 512, 516, 520, 605, 902, 906, the parentnode 702, 802, the child node 704, 804; the apparatus 1102/1102′; theprocessing system 1214, which may include the memory 360 and which maybe the entire IAB node or UE 350 or a component of the IAB node or UE350, such as the TX processor 368, the RX processor 356, and/or thecontroller/processor 359). The first node may communicate with a secondnode, such as another IAB node or UE. For example, the first node may bethe parent node 702, 802, and the second node may be the child node 704,804. Alternatively, the first node may be the child node 704, 804, andthe second node may be the parent node 702, 802. Optional aspects areillustrated in dashed lines. The method allows the first node to performmore efficient communication with the second node based on amultiplexing capability of the first node using, e.g., SDM.

At 1002, the first node may perform a local interference measurement ofone or more beams for communicating with the second node. For example,1002 may be performed by interference measurement component 1108. Forinstance, referring to FIG. 8 , a child node 804 may perform a localinterference measurement 805. For example, the child node 804 mayperform one or more of a self-interference measurement or a cross-beaminterference measurement. Performing an interference measurement mayinclude receiving a signal and determining the interference measurementbased on the received signal.

At 1004, the first node transmits a report to a CU, where the reportincludes at least one multiplexing capability of the first node orincludes at least one multiplexing capability condition for the at leastone multiplexing capability of the first node. For example, 1004 may beperformed by transmission report component 1112. The at least onemultiplexing capability comprises at least one of SDM or FDM, and theSDM includes at least one of SDM FD or SDM HD. For instance, referringto FIG. 8 , the parent node 802 or the child node 804 may respectivelytransmit a report 808, 810 including a SDM FD or HD capability orconditions to a central unit 806. The report may be transmitted by achild node, a parent node, or both a child node and a parent node. In anaspect, reports transmitted by a child node may be optional.

The report may also include the local interference measurement. One ormore of the reports may include, but are not limited to beam/channelquality measurements, CLI measurements, RRM measurements, traffic/loadreport, SDM FD or SDM HD capability and SDM FD or SDM HD conditions,e.g. what pairs of beams or pairs of links may be transmitted using anSDM associated with them, and when there may be any limitation on thelink-budget (e.g., max TX or RX power). One or more of the reports mayinclude a report of SI or cross-beam interference measurements.

The at least one multiplexing capability is also with respect to one ormore transmission direction combinations of the first node. For example,the first node may include a MT and a DU, and the one or moretransmission direction combinations may comprise at least one of MTtransmission and DU transmission, MT transmission and DU reception, MTreception and DU transmission, or MT reception and DU reception. Forinstance, referring to FIG. 8 , the report 808, 810 may indicate SDM orFDM capability of the parent node or child node with respect totransmission-direction combinations including MT-TX/DU-TX (the MTtransmits while the DU transmits), MT-TX/DU-RX (the MT transmits whilethe DU receives), MT-RX/DU-TX (the MT receives while the DU transmits),and MT-RX/DU-RX (the MT receives while the DU receives).

In one example, the at least one multiplexing capability may be for SDMFD, and the one or more beams may comprise a transmission beam and areception beam of the first node. For instance, referring to FIG. 8 ,for SDM (FD) operation, the child node 804 may measure self-interferencefor different combinations of TX/RX beams.

In another example, the at least one multiplexing capability may be forSDM HD, and the one or more beams may comprise a plurality oftransmission beams of the first node or a plurality of reception beamsof the first node. For instance, referring to FIG. 8 , for SDM (HD)operation, the child node 804 may measure cross-beam interference, inwhich a transmission (or reception) over one beam of the child node mayinterfere with a transmission (or reception) over another beam of thechild node.

The at least one multiplexing capability condition may comprise at leastone of: one or more beams to be used for SDM; or a link budget of thefirst node. For example, referring to FIG. 8 , if the SDM capability isconditional, the report 810 to the CU may include the SDM FD or SDM HDconditions of the child node (e.g. beams that may be used for SDM, linkbudget requirements, the links or beam pairs available for SDM, and/orthe physical channels available for SDM).

At 1006, the first node receives a semi-static resource allocation fromthe CU based on the at least one multiplexing capability. For example,1006 may be performed by receive semi-static resource component 1114.For instance, referring to FIG. 8 , the parent node 802 or the childnode 804 may receive a semi-static resource allocation 812 from thecentral unit 806 for communicating with each other using SDM.

At 1008, the first node may receive, from the CU, one or more resourceconditions for using allocated resources of the semi-static resourceallocation. For example, 1008 may be performed by receive conditionscomponent 1116. For instance, referring to FIG. 8 , the parent node 802or the child node 804 may receive conditions 814 for use of resourcesfrom the central unit 806. The conditions may be received by one or morenodes. The one or more nodes may be one or more child nodes and/or oneor more parent nodes. At least one of the semi-static resourceallocation or the conditions for use of resources may be based on thereport.

The one or more resource conditions may indicate whether the allocatedresources are conditional or unconditional for communicating with thesecond node. For instance, referring to FIG. 8 , the conditions 814 mayindicate whether a set of allocated time-domain resources may be usedunconditionally or not for SDM Full-duplex or Half-duplex operation.Conditions 814 may include the directional conditions (D/U/F) describedabove, as well as additional conditions for conditional use. Forexample, in a case of conditional use, the CU 806 may further indicateas conditions 814 various constraints such as those on modulation codingscheme (MCS, e.g. the maximum MCS used over the allocated resources),transmit (Tx) power (e.g. the maximum Tx power that may be used),receive (Rx) power (e.g. the maximum Rx power that may be used), TX/RXbeam(s) that may be used (e.g. the subset of beams or beam pairs/linksthat may be used), frequency-domain resources (e.g. the limited RBs thatmay be used over an indicated set of time domain resources in thesemi-static resource allocation), reference signalconfiguration/resources (e.g. the specific tones or resources that DMRSor another reference signal may be transmitted), and timing reference(e.g. the Tx/Rx timing to be used for alignment with other simultaneouscommunications).

In one example, the first node may be a parent node and the second nodemay be a child node, and the one or more resource conditions mayidentify at least one expected behavior of the parent node with respectto the allocated resources for communicating with the child node. Theallocated resources may comprise one of hard resources or softresources. For instance, referring to FIG. 8 , semi-static resourceallocation 812 and/or conditions 814 may identify an expected behaviorof the parent node 802 as an alternative to aforementioned conflictresolution rules. For example, if the resource allocation for a same setof resources is (HARD∥HARD), the conditions 814 may indicate to theparent node 802 an expected behavior not to yield the resources for useby its children when the child node 804 has HD or FD capability. Inanother example, the conditions 814 may indicate to the parent node anexpected behavior not to refrain from using released soft resources whencommunicating with the child node.

In another example, the first node may be a child node and the secondnode may be a parent node, and the one or more resource conditions mayidentify at least one expected behavior of the child node with respectto the allocated resources for communicating with the parent node. Forinstance, referring to FIG. 8 , the conditions 814 may indicate to thechild node 804 an expected behavior not to refrain from using unreleased(or reclaimed) soft resources when communicating with its own childnodes or the parent node 802.

At 1010, the first node may transmit a change request to the CU tomodify the semi-static resource allocation, where the at least onemultiplexing capability may be enabled based on the modified semi-staticresource allocation. For example, 1010 may be performed by transmitchange request component 1118. For instance, referring to FIG. 8 , theparent node 802 or the child node 804 may respectively transmit a changerequest 816, 818 to the CU 806 to modify at least one of the semi-staticresource allocation 812 or the conditions 814 for use of resources. Inan aspect, the change request may include a request to enable or disableat least one of SDM FD or SDM HD.

At 1012, the first node may modify at least one of a transmission beamor a reception beam based on the local interference measurement. Forexample, 1012 may be performed by a modify beams component 1110. Forinstance, referring to FIG. 8 , the parent node 802 or the child node804 may modify, at 820 and 822 respectively, at least one of a transmitor a receive beam based on at least one of the semi-static resourceallocation 812 or the conditions 814 for use of resources, where thesemi-static resource allocation 812 or the conditions 814 may beindicated based on the report 810 sent to the CU 806 including the localinterference measurement 805. For example, the parent node 802 or thechild node 804 may modify beams by processing at least one of thesemi-static resource allocation or the conditions for use of resourcesto determine a modification and implementing the modification to the atleast one of a transmit or a receive beam.

Finally, at 1014, the first node communicates with a second node basedon the semi-static resource allocation. The communication with thesecond node may also be based on the one or more resource conditions.For example, 1014 may be performed by establish FD component 1120. Forinstance, referring to FIG. 8 , the parent node 802 or the child node804 may establish a FD connection and communicate with each other at 824or 826 using at least one of a hard resource or a soft resource based onat least one of the semi-static resource allocation 812 or theconditions 814 for use of resources received based on the report 810 tothe CU 806.

FIG. 11 is a conceptual data flow diagram 1100 illustrating the dataflow between different means/components in an example apparatus 1102.The apparatus may be a first node in communication with a second node1150 and a CU 1160 (e.g. CU 806). The apparatus may be, e.g., parentnode 802, and the second node may be, e.g., child node 804.Alternatively, the apparatus may be, e.g., child node 804, and thesecond node may be, e.g., parent node 802.

The apparatus 1102 includes a reception component 1104 that isconfigured to receives communications from the second node 1150 and CU1160. For example, the reception component may receive semi-staticresource allocations from the CU and data from the second node. Theapparatus also includes a transmission component 1106 that is configuredto transmit communications to the second node and CU. For example, thetransmission component may transmit reports to the CU and data to thesecond node.

The apparatus 1102 may include an interference measurement component1108 that is configured to perform a local interference measurement ofone or more beams for communicating with the second node, e.g., asdescribed in connection with 1002. The apparatus may include a modifybeams component 1110 that is configured to modify at least one of atransmission beam or a reception beam based on the local interferencemeasurement, e.g., as described in connection with 1012. The apparatus(e.g. the transmission component 1106) may include a transmission reportcomponent 1112 that is configured to transmit a report to the CU, wherethe report includes at least one multiplexing capability of the firstnode or includes at least one multiplexing capability condition for theat least one multiplexing capability of the first node, e.g., asdescribed in connection with 1004. The apparatus (e.g. the receptioncomponent 1104) may include a receive semi-static resource component1114 that is configured to receive a semi-static resource allocationfrom the CU based on the at least one multiplexing capability (includedin the report from transmission report component 1112), e.g., asdescribed in connection with 1006.

The apparatus 1102 (e.g. the reception component 1104) may include areceive conditions component 1116 that is configured to receive, fromthe CU 1160, one or more resource conditions for using allocatedresources of the semi-static resource allocation, e.g., as described inconnection with 1008. The apparatus (e.g. the transmission component1106) may include a transmit change request component 1118 that isconfigured to transmit a change request to the CU to modify thesemi-static resource allocation (received by receive conditionscomponent 1116), e.g., as described in connection with 1010. Theapparatus may include an establish FD component 1120 that is configuredto communicate with the second node 1150 based on the semi-staticresource allocation and on the one or more resource conditions (receivedby receive conditions component 1116), e.g., as described in connectionwith 1014.

The apparatus may include additional components that perform each of theblocks of the algorithm in the aforementioned flowcharts of FIG. 10 . Assuch, each block in the aforementioned flowcharts of FIG. 10 may beperformed by a component and the apparatus may include one or more ofthose components. The components may be one or more hardware componentsspecifically configured to carry out the stated processes/algorithm,implemented by a processor configured to perform the statedprocesses/algorithm, stored within a computer-readable medium forimplementation by a processor, or some combination thereof.

FIG. 12 is a diagram 1200 illustrating an example of a hardwareimplementation for an apparatus 1102′ employing a processing system1214. The processing system 1214 may be implemented with a busarchitecture, represented generally by the bus 1224. The bus 1224 mayinclude any number of interconnecting buses and bridges depending on thespecific application of the processing system 1214 and the overalldesign constraints. The bus 1224 links together various circuitsincluding one or more processors and/or hardware components, representedby the processor 1204, the components 1104, 1106, 1108, 1110, 1112,1114, 1116, 1118, 1120 and the computer-readable medium/memory 1206. Thebus 1224 may also link various other circuits such as timing sources,peripherals, voltage regulators, and power management circuits, whichare well known in the art, and therefore, will not be described anyfurther.

The processing system 1214 may be coupled to a transceiver 1210. Thetransceiver 1210 is coupled to one or more antennas 1220. Thetransceiver 1210 provides a means for communicating with various otherapparatus over a transmission medium. The transceiver 1210 receives asignal from the one or more antennas 1220, extracts information from thereceived signal, and provides the extracted information to theprocessing system 1214, specifically the reception component 1104. Inaddition, the transceiver 1210 receives information from the processingsystem 1214, specifically the transmission component 1106, and based onthe received information, generates a signal to be applied to the one ormore antennas 1220. The processing system 1214 includes a processor 1204coupled to a computer-readable medium/memory 1206. The processor 1204 isresponsible for general processing, including the execution of softwarestored on the computer-readable medium/memory 1206. The software, whenexecuted by the processor 1204, causes the processing system 1214 toperform the various functions described supra for any particularapparatus. The computer-readable medium/memory 1206 may also be used forstoring data that is manipulated by the processor 1204 when executingsoftware. The processing system 1214 further includes at least one ofthe components 1104, 1106, 1108, 1110, 1112, 1114, 1116, 1118, 1120. Thecomponents may be software components running in the processor 1204,resident/stored in the computer readable medium/memory 1206, one or morehardware components coupled to the processor 1204, or some combinationthereof. The processing system 1214 may be a component of an IAB node(e.g. IAB node 402) or the UE 350 and may include the memory 360 and/orat least one of the TX processor 368, the RX processor 356, and thecontroller/processor 359. Alternatively, the processing system 1214 maybe the entire IAB node or UE (e.g., see 350 of FIG. 3 ).

In one configuration, the apparatus 1102/1102′ for wirelesscommunication includes means for transmitting a report to a central unit(CU), wherein the report includes at least one multiplexing capabilityof the first node or includes at least one multiplexing capabilitycondition for the at least one multiplexing capability of the firstnode; means for receiving a semi-static resource allocation from the CUbased on the at least one multiplexing capability; and means forcommunicating with a second node based on the semi-static resourceallocation; wherein the at least one multiplexing capability comprisesat least one of Spatial Division Multiplexing (SDM) or FrequencyDivision Multiplexing (FDM), and wherein the SDM includes at least oneof SDM Full Duplex (SDM FD) or SDM Half-Duplex (SDM HD); and wherein theat least one multiplexing capability is with respect to one or moretransmission direction combinations of the first node.

In one configuration, the apparatus 1102/1102′ may include means forperforming a local interference measurement of one or more beams forcommunicating with the second node; and wherein the report includes thelocal interference measurement.

In one configuration, the apparatus 1102/1102′ may include means formodifying at least one of the transmission beam or the reception beambased on the local interference measurement.

In one configuration, the apparatus 1102/1102′ may include means forreceiving, from the CU, one or more resource conditions for usingallocated resources of the semi-static resource allocation; wherein thecommunicating with the second node is based on the one or more resourceconditions.

In one configuration, the apparatus 1102/1102′ may include means fortransmitting a change request to the CU to modify the semi-staticresource allocation; wherein the at least one multiplexing capability isenabled based on the modified semi-static resource allocation.

The aforementioned means may be one or more of the aforementionedcomponents of the apparatus 1102 and/or the processing system 1214 ofthe apparatus 1102′ configured to perform the functions recited by theaforementioned means. As described supra, the processing system 1214 mayinclude the TX Processor 368, the RX Processor 356, and thecontroller/processor 359. As such, in one configuration, theaforementioned means may be the TX Processor 368, the RX Processor 356,and the controller/processor 359 configured to perform the functionsrecited by the aforementioned means.

FIG. 13 is a flowchart 1300 of a method of wireless communication. Themethod may be performed by a central unit, such as an IAB node or basestation (e.g., the base station 102/180, 310, the IAB node 402, 606, thecentral unit 706, 806; the apparatus 1402/1402′; the processing system1514, which may include the memory 376 and which may be the entirecentral unit, IAB node or base station 310 or a component of the centralunit, IAB node or base station 310, such as the TX processor 316, the RXprocessor 370, and/or the controller/processor 375). The central unitmay communicate with a first node and a second node, such as an IAB nodeor UE. For example, the first node may be the parent node 702, 802, andthe second node may be the child node 704, 804. Alternatively, the firstnode may be the child node 704, 804, and the second node may be theparent node 702, 802. Optional aspects are illustrated in dashed lines.The method allows the central unit to provide more efficient capabilityto the first node for communicating with the second node based on amultiplexing capability of the first node using, e.g., SDM.

At 1302, the central unit receives a report from a first node, where thereport includes at least one multiplexing capability of the first nodeor includes at least one multiplexing capability condition for the atleast one multiplexing capability of the first node. For example, 1302may be performed by receive report component 1408. For instance,referring to FIG. 8 , the central unit 806 may receive a report 808, 810respectively from a parent node 802 or a child node 804. The report maybe received from a child node, a parent node, or both a child node and aparent node. In an aspect, reports from a child node may be optional.One or more of the reports may include, but are not limited to,beam/channel quality measurements, CLI measurements, RRM measurements,traffic/load report, SDM FD or SDM HD capability and SDM FD or SDM HDconditions, e.g. what pairs of beams or pairs of links may betransmitted using SDM, and any limitation on the link-budget (e.g., maxTX or RX power). One or more of the reports may include a report of SIor cross-beam interference measurements.

At 1304, the central unit may transmit to a second node an indication ofthe at least one multiplexing capability or the at least onemultiplexing capability condition. For example, 1304 may be performed bycapability indication component 1410. For instance, referring to FIG. 8, when the CU 806 receives the report 810 from the child node 804, theCU may transmit to the parent node 802 an indication of the capabilityor conditions of the child node. The report 808 from the parent node 802may similarly include SDM capability and/or conditions of the parentnode, and the CU 806 may similarly transmit to the child node 804 anindication of the capability or conditions of the parent node.

At 1306, the central unit transmits to the first node a semi-staticresource allocation based on the at least one multiplexing capabilityfor communication of the first node with a second node. The at least onemultiplexing capability comprises at least one of SDM or FDM, and theSDM includes at least one of SDM FD or SDM HD. For example, 1306 may beperformed by transmit semi-static resource component 1412. For instance,referring to FIG. 8 , the central unit 806 may transmit a semi-staticresource allocation 812 to one or more nodes including the parent node802 or child node 804 to use for communicating using SDM. The one ormore nodes may be one or more child nodes 804 and/or one or more parentnodes 802. The semi-static resources may include, but are not limited toallocation information for time-domain resources.

The at least one multiplexing capability is also with respect to one ormore transmission direction combinations of the first node. For example,the first node may include a MT and a DU, and the one or moretransmission direction combinations may comprise at least one of MTtransmission and DU transmission, MT transmission and DU reception, MTreception and DU transmission, or MT reception and DU reception. Forinstance, referring to FIG. 8 , the report 808, 810 may indicate SDM orFDM capability of the parent node or child node with respect totransmission-direction combinations including MT-TX/DU-TX (the MTtransmits while the DU transmits), MT-TX/DU-RX (the MT transmits whilethe DU receives), MT-RX/DU-TX (the MT receives while the DU transmits),and MT-RX/DU-RX (the MT receives while the DU receives).

The at least one multiplexing capability condition may comprise at leastone of: one or more beams to be used for SDM; or a link budget of thefirst node. For example, referring to FIG. 8 , if the SDM capability isconditional, the report 810 to the CU may include the SDM FD or SDM HDconditions of the child node (e.g. beams that may be used for SDM, linkbudget requirements, the links or beam pairs available for SDM, and/orthe physical channels available for SDM).

At 1308, the central unit may transmit, to the first node, one or moreresource conditions for using allocated resources of the semi-staticresource allocation. The communication of the first node with the secondnode may be based on the one or more resource conditions. For example,1308 may be performed by transmit conditions component 1414. Forinstance, referring to FIG. 8 , the central unit 806 may transmitconditions 814 for use of resources to one or more nodes. The one ormore nodes may be one or more child nodes 804 and/or one or more parentnodes 802. At least one of the semi-static resource allocation 812 orthe conditions 814 for use of resources may be based on the report 808,810.

The one or more resource conditions may indicate whether the allocatedresources are conditional or unconditional for communication of thefirst node with the second node. For instance, referring to FIG. 8 , theconditions 814 may indicate whether a set of allocated time-domainresources may be used unconditionally or not for SDM Full-duplex orHalf-duplex operation. Conditions 814 may include the directionalconditions (D/U/F) described above, as well as additional conditions forconditional use. For example, in a case of conditional use, the CU 806may further indicate as conditions 814 various constraints such as thoseon modulation coding scheme (MCS, e.g. the maximum MCS used over theallocated resources), transmit (Tx) power (e.g. the maximum Tx powerthat may be used), receive (Rx) power (e.g. the maximum Rx power thatmay be used), TX/RX beam(s) that may be used (e.g. the subset of beamsor beam pairs/links that may be used), frequency-domain resources (e.g.the limited RBs that may be used over an indicated set of time domainresources in the semi-static resource allocation), reference signalconfiguration/resources (e.g. the specific tones or resources that DMRSor another reference signal may be transmitted), and timing reference(e.g. the Tx/Rx timing to be used for alignment with other simultaneouscommunications).

In one example, the first node may be a parent node and the second nodemay be a child node, and the one or more resource conditions mayidentify at least one expected behavior of the parent node with respectto the allocated resources for communicating with the child node. Theallocated resources may comprise one of hard resources or softresources. For instance, referring to FIG. 8 , semi-static resourceallocation 812 and/or conditions 814 may identify an expected behaviorof the parent node 802 as an alternative to aforementioned conflictresolution rules. For example, if the resource allocation for a same setof resources is (HARD∥HARD), the conditions 814 may indicate to theparent node 802 an expected behavior not to yield the resources for useby its children when the child node 804 has HD or FD capability. Inanother example, the conditions 814 may indicate to the parent node anexpected behavior not to refrain from using released soft resources whencommunicating with the child node.

In another example, the first node may be a child node and the secondnode may be a parent node, and the one or more resource conditions mayidentify at least one expected behavior of the child node with respectto the allocated resources for communicating with the parent node. Forinstance, referring to FIG. 8 , the conditions 814 may indicate to thechild node 804 an expected behavior not to refrain from using unreleased(or reclaimed) soft resources when communicating with its own childnodes or the parent node 802.

Finally, at 1310, the central unit may receive a change request from thefirst node to modify the semi-static resource allocation. The at leastone multiplexing capability may be enabled for the first node based onthe modified semi-static resource allocation. For example, 1310 may beperformed by receive change request component 1416. For instance,referring to FIG. 8 , the central unit 806 may receive a change request816, 818 respectively from the parent node 802 or child node 804 tomodify at least one of the semi-static resource allocation 812 or theconditions 814 for use of resources. The change request may be receivedfrom a child node, a parent node, or both a child node and a parentnode. In an aspect, the change request may include a request to enableor disable at least one of SDM FD or SDM HD.

FIG. 14 is a conceptual data flow diagram 1400 illustrating the dataflow between different means/components in an example apparatus 1402.The apparatus may be a CU (e.g. CU 806) in communication with a firstnode 1450 and a second node 1460. The first node may be, e.g., parentnode 802, and the second node may be, e.g., child node 804.Alternatively, the first may be, e.g., child node 804, and the secondnode may be, e.g., parent node 802.

The apparatus 1402 includes a reception component 1404 that isconfigured to receive communications from the first node 1450 and secondnode 1460. For example, the reception component may receive reports andchange requests from the first node and the second node. The apparatusalso includes a transmission component 1406 that is configured totransmit communications to the first node and the second node. Forexample, the transmission component may transmit semi-static resourceallocations and resource conditions to the first node and the secondnode.

The apparatus 1402 (e.g. the reception component 1404) includes areceive report component 1408 that is configured to receive a reportfrom a first node, where the report includes at least one multiplexingcapability of the first node or includes at least one multiplexingcapability condition for the at least one multiplexing capability of thefirst node, e.g., as described in connection with 1302. The apparatusmay include a capability indication component 1410 that is configured totransmit to a second node an indication of the at least one multiplexingcapability or the at least one multiplexing capability condition (basedon the report from receive report component 1408), e.g., as described inconnection with 1304. The apparatus includes a transmit semi-staticresource component 1412 that is configured to transmit to the first nodea semi-static resource allocation based on the at least one multiplexingcapability for communication of the first node with a second node, e.g.,as described in connection with 1306. The apparatus may include atransmit conditions component 1414 that is configured to transmit, tothe first node, one or more resource conditions for using allocatedresources of the semi-static resource allocation, e.g., as described inconnection with 1308. The apparatus may include a receive change requestcomponent 1416 that is configured to receive a change request from thefirst node to modify the semi-static resource allocation, e.g., asdescribed in connection with 1310.

The apparatus may include additional components that perform each of theblocks of the algorithm in the aforementioned flowchart of FIG. 13 . Assuch, each block in the aforementioned flowchart of FIG. 13 may beperformed by a component and the apparatus may include one or more ofthose components. The components may be one or more hardware componentsspecifically configured to carry out the stated processes/algorithm,implemented by a processor configured to perform the statedprocesses/algorithm, stored within a computer-readable medium forimplementation by a processor, or some combination thereof.

FIG. 15 is a diagram 1500 illustrating an example of a hardwareimplementation for an apparatus 1402′ employing a processing system1514. The processing system 1514 may be implemented with a busarchitecture, represented generally by the bus 1524. The bus 1524 mayinclude any number of interconnecting buses and bridges depending on thespecific application of the processing system 1514 and the overalldesign constraints. The bus 1524 links together various circuitsincluding one or more processors and/or hardware components, representedby the processor 1504, the components 1404, 1406, 1408, 1410, 1412,1414, 1416 and the computer-readable medium/memory 1506. The bus 1524may also link various other circuits such as timing sources,peripherals, voltage regulators, and power management circuits, whichare well known in the art, and therefore, will not be described anyfurther.

The processing system 1514 may be coupled to a transceiver 1510. Thetransceiver 1510 is coupled to one or more antennas 1520. Thetransceiver 1510 provides a means for communicating with various otherapparatus over a transmission medium. The transceiver 1510 receives asignal from the one or more antennas 1520, extracts information from thereceived signal, and provides the extracted information to theprocessing system 1514, specifically the reception component 1404. Inaddition, the transceiver 1510 receives information from the processingsystem 1514, specifically the transmission component 1406, and based onthe received information, generates a signal to be applied to the one ormore antennas 1520. The processing system 1514 includes a processor 1504coupled to a computer-readable medium/memory 1506. The processor 1504 isresponsible for general processing, including the execution of softwarestored on the computer-readable medium/memory 1506. The software, whenexecuted by the processor 1504, causes the processing system 1514 toperform the various functions described supra for any particularapparatus. The computer-readable medium/memory 1506 may also be used forstoring data that is manipulated by the processor 1504 when executingsoftware. The processing system 1514 further includes at least one ofthe components 1404, 1406, 1408, 1410, 1412, 1414, 1416. The componentsmay be software components running in the processor 1504,resident/stored in the computer readable medium/memory 1506, one or morehardware components coupled to the processor 1504, or some combinationthereof. The processing system 1514 may be a component of a CU (e.g. CU706, 806 of an IAB node 606) or the base station 310 and may include thememory 376 and/or at least one of the TX processor 316, the RX processor370, and the controller/processor 375. Alternatively, the processingsystem 1514 may be the entire CU, IAB node, or base station (e.g., see310 of FIG. 3 ).

In one configuration, the apparatus 1402/1402′ for wirelesscommunication includes means for receiving a report from a first node,wherein the report includes at least one multiplexing capability of thefirst node or includes at least one multiplexing capability conditionfor the at least one multiplexing capability of the first node; andmeans for transmitting to the first node a semi-static resourceallocation based on the at least one multiplexing capability forcommunication of the first node with a second node; wherein the at leastone multiplexing capability comprises at least one of Spatial DivisionMultiplexing (SDM) or Frequency Division Multiplexing (FDM), and whereinthe SDM includes at least one of SDM Full Duplex (SDM FD) or SDMHalf-Duplex (SDM HD); and wherein the at least one multiplexingcapability is with respect to one or more transmission directioncombinations of the first node.

In one configuration, the apparatus 1402/1402′ may include means fortransmitting to the second node an indication of the at least onemultiplexing capability or the at least one multiplexing capabilitycondition.

In one configuration, the apparatus 1402/1402′ may include means fortransmitting, to the first node, one or more resource conditions forusing allocated resources of the semi-static resource allocation;wherein the communication of the first node with the second node isbased on the one or more resource conditions.

In one configuration, the apparatus 1402/1402′ may include means forreceiving a change request from the first node to modify the semi-staticresource allocation; wherein the at least one multiplexing capability isenabled for the first node based on the modified semi-static resourceallocation.

The aforementioned means may be one or more of the aforementionedcomponents of the apparatus 1402 and/or the processing system 1514 ofthe apparatus 1402′ configured to perform the functions recited by theaforementioned means. As described supra, the processing system 1514 mayinclude the TX Processor 316, the RX Processor 370, and thecontroller/processor 375. As such, in one configuration, theaforementioned means may be the TX Processor 316, the RX Processor 370,and the controller/processor 375 configured to perform the functionsrecited by the aforementioned means.

FIG. 16 is a flowchart 1600 of a method of wireless communication. Themethod may be performed by a first node, such as an IAB node or UE(e.g., the UE 104, 350, 514, the IAB node 402, 414, 416, 424, 426, 434,436, 501, 503, 506, 506, 510, 512, 516, 520, 605, 902, 906, the parentnode 702, 802, the child node 704, 804; the apparatus 1702/1702′; theprocessing system 1814, which may include the memory 360 and which maybe the entire IAB node or UE 350 or a component of the IAB node or UE350, such as the TX processor 368, the RX processor 356, and/or thecontroller/processor 359). The first node may communicate with a secondnode, such as another IAB node or UE. For example, the first node may bethe parent node 702, 802, and the second node may be the child node 704,804. Alternatively, the first node may be the child node 704, 804, andthe second node may be the parent node 702, 802. Optional aspects areillustrated in dashed lines. The method allows the first node to performmore efficient communication with the second node based on amultiplexing capability of the first node using, e.g., SDM.

At 1602, the first node may perform a local interference measurement ofone or more beams for communicating with the second node. For example,1602 may be performed by interference measurement component 1708. Forinstance, referring to FIG. 8 , a child node 804 may perform a localinterference measurement 805. For example, the child node 804 mayperform one or more of a self-interference measurement or a cross-beaminterference measurement. Performing an interference measurement mayinclude receiving a signal and determining the interference measurementbased on the received signal.

At 1604, the first node may transmit a report to a CU, where the reportincludes at least one multiplexing capability of the first node orincludes at least one multiplexing capability condition for the at leastone multiplexing capability of the first node. For example, 1604 may beperformed by transmission report component 1712. The at least onemultiplexing capability comprises at least one of SDM or FDM, and theSDM includes at least one of SDM FD or SDM HD. For instance, referringto FIG. 8 , the parent node 802 or the child node 804 may respectivelytransmit a report 808, 810 including a SDM FD or HD capability orconditions to a central unit 806. The report may be transmitted by achild node, a parent node, or both a child node and a parent node. In anaspect, reports transmitted by a child node may be optional.

The report may also include the local interference measurement. One ormore of the reports may include, but are not limited to beam/channelquality measurements, CLI measurements, RRM measurements, traffic/loadreport, SDM FD or SDM HD capability and SDM FD or SDM HD conditions,e.g. what pairs of beams or pairs of links may be transmitted using anSDM associated with them, and when there may be any limitation on thelink-budget (e.g., max TX or RX power). One or more of the reports mayinclude a report of SI or cross-beam interference measurements.

The at least one multiplexing capability is also with respect to one ormore transmission direction combinations of the first node. For example,the first node may include a MT and a DU, and the one or moretransmission direction combinations may comprise at least one of MTtransmission and DU transmission, MT transmission and DU reception, MTreception and DU transmission, or MT reception and DU reception. Forinstance, referring to FIG. 8 , the report 808, 810 may indicate SDM orFDM capability of the parent node or child node with respect totransmission-direction combinations including MT-TX/DU-TX (the MTtransmits while the DU transmits), MT-TX/DU-RX (the MT transmits whilethe DU receives), MT-RX/DU-TX (the MT receives while the DU transmits),and MT-RX/DU-RX (the MT receives while the DU receives).

In one example, the at least one multiplexing capability may be for SDMFD, and the one or more beams may comprise a transmission beam and areception beam of the first node. For instance, referring to FIG. 8 ,for SDM (FD) operation, the child node 804 may measure self-interferencefor different combinations of TX/RX beams.

In another example, the at least one multiplexing capability may be forSDM HD, and the one or more beams may comprise a plurality oftransmission beams of the first node or a plurality of reception beamsof the first node. For instance, referring to FIG. 8 , for SDM (HD)operation, the child node 804 may measure cross-beam interference, inwhich a transmission (or reception) over one beam of the child node mayinterfere with a transmission (or reception) over another beam of thechild node.

The at least one multiplexing capability condition may comprise at leastone of: one or more beams to be used for SDM; or a link budget of thefirst node. For example, referring to FIG. 8 , if the SDM capability isconditional, the report 810 to the CU may include the SDM FD or SDM HDconditions of the child node (e.g. beams that may be used for SDM, linkbudget requirements, the links or beam pairs available for SDM, and/orthe physical channels available for SDM).

At 1606, the first node receives a semi-static resource allocation fromthe CU based on the at least one multiplexing capability of the firstnode. For example, 1606 may be performed by receive semi-static resourcecomponent 1714. For instance, referring to FIG. 8 , the parent node 802or the child node 804 may receive a semi-static resource allocation 812from the central unit 806 for communicating with each other using SDM.

At 1608, the first node receives, from the CU, one or more resourceconditions for using allocated resources of the semi-static resourceallocation. For example, 1608 may be performed by receive conditionscomponent 1716. For instance, referring to FIG. 8 , the parent node 802or the child node 804 may receive conditions 814 for use of resourcesfrom the central unit 806. The conditions may be received by one or morenodes. The one or more nodes may be one or more child nodes and/or oneor more parent nodes. At least one of the semi-static resourceallocation or the conditions for use of resources may be based on thereport.

The one or more resource conditions may indicate whether the allocatedresources are conditional or unconditional for communicating with thesecond node. For instance, referring to FIG. 8 , the conditions 814 mayindicate whether a set of allocated time-domain resources may be usedunconditionally or not for SDM Full-duplex or Half-duplex operation.Conditions 814 may include the directional conditions (D/U/F) describedabove, as well as additional conditions for conditional use. Forexample, in a case of conditional use, the CU 806 may further indicateas conditions 814 various constraints such as those on modulation codingscheme (MCS, e.g. the maximum MCS used over the allocated resources),transmit (Tx) power (e.g. the maximum Tx power that may be used),receive (Rx) power (e.g. the maximum Rx power that may be used), TX/RXbeam(s) that may be used (e.g. the subset of beams or beam pairs/linksthat may be used), frequency-domain resources (e.g. the limited RBs thatmay be used over an indicated set of time domain resources in thesemi-static resource allocation), reference signalconfiguration/resources (e.g. the specific tones or resources that DMRSor another reference signal may be transmitted), and timing reference(e.g. the Tx/Rx timing to be used for alignment with other simultaneouscommunications).

In one example, the first node may be a parent node and the second nodemay be a child node, and the one or more resource conditions mayidentify at least one expected behavior of the parent node with respectto the allocated resources for communicating with the child node. Theallocated resources may comprise one of hard resources or softresources. For instance, referring to FIG. 8 , semi-static resourceallocation 812 and/or conditions 814 may identify an expected behaviorof the parent node 802 as an alternative to aforementioned conflictresolution rules. For example, if the resource allocation for a same setof resources is (HARD∥HARD), the conditions 814 may indicate to theparent node 802 an expected behavior not to yield the resources for useby its children when the child node 804 has HD or FD capability. Inanother example, the conditions 814 may indicate to the parent node anexpected behavior not to refrain from using released soft resources whencommunicating with the child node.

In another example, the first node may be a child node and the secondnode may be a parent node, and the one or more resource conditions mayidentify at least one expected behavior of the child node with respectto the allocated resources for communicating with the parent node. Forinstance, referring to FIG. 8 , the conditions 814 may indicate to thechild node 804 an expected behavior not to refrain from using unreleased(or reclaimed) soft resources when communicating with its own childnodes or the parent node 802.

At 1610, the first node may transmit a change request to the CU tomodify the semi-static resource allocation, where the at least onemultiplexing capability may be enabled based on the modified semi-staticresource allocation. For example, 1610 may be performed by transmitchange request component 1718. For instance, referring to FIG. 8 , theparent node 802 or the child node 804 may respectively transmit a changerequest 816, 818 to the CU 806 to modify at least one of the semi-staticresource allocation 812 or the conditions 814 for use of resources. Inan aspect, the change request may include a request to enable or disableat least one of SDM FD or SDM HD.

At 1612, the first node may modify at least one of a transmission beamor a reception beam based on the local interference measurement. Forexample, 1612 may be performed by a modify beams component 1710. Forinstance, referring to FIG. 8 , the parent node 802 or the child node804 may modify, at 820 and 822 respectively, at least one of a transmitor a receive beam based on at least one of the semi-static resourceallocation 812 or the conditions 814 for use of resources, where thesemi-static resource allocation 812 or the conditions 814 may beindicated based on the report 810 sent to the CU 806 including the localinterference measurement 805. For example, the parent node 802 or thechild node 804 may modify beams by processing at least one of thesemi-static resource allocation or the conditions for use of resourcesto determine a modification and implementing the modification to the atleast one of a transmit or a receive beam.

Finally, at 1614, the first node communicates with a second node basedon the semi-static resource allocation. The communication with thesecond node may also be based on the one or more resource conditions.For example, 1614 may be performed by establish FD component 1720. Forinstance, referring to FIG. 8 , the parent node 802 or the child node804 may establish a FD connection and communicate with each other at 824or 826 using at least one of a hard resource or a soft resource based onat least one of the semi-static resource allocation 812 or theconditions 814 for use of resources received based on the report 810 tothe CU 806.

FIG. 17 is a conceptual data flow diagram 1700 illustrating the dataflow between different means/components in an example apparatus 1702.The apparatus may be a first node in communication with a second node1750 and a CU 1760 (e.g. CU 806). The apparatus may be, e.g., parentnode 802, and the second node may be, e.g., child node 804.Alternatively, the apparatus may be, e.g., child node 804, and thesecond node may be, e.g., parent node 802.

The apparatus 1702 includes a reception component 1704 that isconfigured to receive communications from the second node 1750 and CU1760. For example, the reception component may receive semi-staticresource allocations from the CU and data from the second node. Theapparatus also includes a transmission component 1706 that is configuredto transmit communications to the second node and CU. For example, thetransmission component may transmit reports to the CU and data to thesecond node.

The apparatus 1702 may include an interference measurement component1708 that is configured to perform a local interference measurement ofone or more beams for communicating with the second node, e.g., asdescribed in connection with 1602. The apparatus may include a modifybeams component 1710 that is configured to modify at least one of atransmission beam or a reception beam based on the local interferencemeasurement, e.g., as described in connection with 1612. The apparatus(e.g. the transmission component 1706) may include a transmission reportcomponent 1712 that is configured to transmit a report to the CU, wherethe report includes at least one multiplexing capability of the firstnode or includes at least one multiplexing capability condition for theat least one multiplexing capability of the first node, e.g., asdescribed in connection with 1604. The apparatus (e.g. the receptioncomponent 1704) may include a receive semi-static resource component1714 that is configured to receive a semi-static resource allocationfrom the CU based on the at least one multiplexing capability (e.g.included in the report from transmission report component 1112), e.g.,as described in connection with 1606.

The apparatus 1702 (e.g. the reception component 1704) may include areceive conditions component 1716 that is configured to receive, fromthe CU 1760, one or more resource conditions for using allocatedresources of the semi-static resource allocation, e.g., as described inconnection with 1608. The apparatus (e.g. the transmission component1706) may include a transmit change request component 1718 that isconfigured to transmit a change request to the CU to modify thesemi-static resource allocation (received by receive conditionscomponent 1716), e.g., as described in connection with 1610. Theapparatus may include an establish FD component 1720 that is configuredto communicate with the second node 1750 based on the semi-staticresource allocation and on the one or more resource conditions (receivedby receive conditions component 1716), e.g., as described in connectionwith 1614.

The apparatus may include additional components that perform each of theblocks of the algorithm in the aforementioned flowchart of FIG. 16 . Assuch, each block in the aforementioned flowchart of FIG. 16 may beperformed by a component and the apparatus may include one or more ofthose components. The components may be one or more hardware componentsspecifically configured to carry out the stated processes/algorithm,implemented by a processor configured to perform the statedprocesses/algorithm, stored within a computer-readable medium forimplementation by a processor, or some combination thereof.

FIG. 18 is a diagram 1800 illustrating an example of a hardwareimplementation for an apparatus 1702′ employing a processing system1814. The processing system 1814 may be implemented with a busarchitecture, represented generally by the bus 1824. The bus 1824 mayinclude any number of interconnecting buses and bridges depending on thespecific application of the processing system 1814 and the overalldesign constraints. The bus 1824 links together various circuitsincluding one or more processors and/or hardware components, representedby the processor 1804, the components 1704, 1706, 1708, 1710, 1712,1714, 1716, 1718, 1720 and the computer-readable medium/memory 1806. Thebus 1824 may also link various other circuits such as timing sources,peripherals, voltage regulators, and power management circuits, whichare well known in the art, and therefore, will not be described anyfurther.

The processing system 1814 may be coupled to a transceiver 1810. Thetransceiver 1810 is coupled to one or more antennas 1820. Thetransceiver 1810 provides a means for communicating with various otherapparatus over a transmission medium. The transceiver 1810 receives asignal from the one or more antennas 1820, extracts information from thereceived signal, and provides the extracted information to theprocessing system 1814, specifically the reception component 1704. Inaddition, the transceiver 1810 receives information from the processingsystem 1814, specifically the transmission component 1706, and based onthe received information, generates a signal to be applied to the one ormore antennas 1820. The processing system 1814 includes a processor 1804coupled to a computer-readable medium/memory 1806. The processor 1804 isresponsible for general processing, including the execution of softwarestored on the computer-readable medium/memory 1806. The software, whenexecuted by the processor 1804, causes the processing system 1814 toperform the various functions described supra for any particularapparatus. The computer-readable medium/memory 1806 may also be used forstoring data that is manipulated by the processor 1804 when executingsoftware. The processing system 1814 further includes at least one ofthe components 1704, 1706, 1708, 1710, 1712, 1714, 1716, 1718, 1720. Thecomponents may be software components running in the processor 1804,resident/stored in the computer readable medium/memory 1806, one or morehardware components coupled to the processor 1804, or some combinationthereof. The processing system 1814 may be a component of an IAB node(e.g. IAB node 402) or the UE 350 and may include the memory 360 and/orat least one of the TX processor 368, the RX processor 356, and thecontroller/processor 359. Alternatively, the processing system 1814 maybe the entire IAB node or UE (e.g., see 350 of FIG. 3 ).

In one configuration, the apparatus 1702/1702′ for wirelesscommunication includes means for receiving a semi-static resourceallocation from a central unit (CU) based on at least one multiplexingcapability of the first node; means for receiving, from the CU, one ormore resource conditions for using allocated resources of thesemi-static resource allocation; and means for communicating with asecond node based on the semi-static resource allocation and the one ormore resource conditions; wherein the at least one multiplexingcapability comprises at least one of Spatial Division Multiplexing (SDM)or Frequency Division Multiplexing (FDM), and wherein the SDM includesat least one of SDM Full Duplex (SDM FD) or SDM Half-Duplex (SDM HD);and wherein the at least one multiplexing capability is with respect toone or more transmission direction combinations of the first node.

In one configuration, the apparatus 1702/1702′ may include means forperforming a local interference measurement of one or more beams forcommunicating with the second node; and wherein the report includes thelocal interference measurement.

In one configuration, the apparatus 1702/1702′ may include means formodifying at least one of the transmission beam or the reception beambased on the local interference measurement.

In one configuration, the apparatus 1702/1702′ may include means fortransmitting a report to the CU, wherein the report may include the atleast one multiplexing capability of the first node or may include atleast one multiplexing capability condition for the at least onemultiplexing capability of the first node, and wherein the semi-staticresource allocation is received based on the report.

In one configuration, the apparatus 1702/1702′ may include means fortransmitting a change request to the CU to modify the semi-staticresource allocation; wherein the at least one multiplexing capability isenabled based on the modified semi-static resource allocation.

The aforementioned means may be one or more of the aforementionedcomponents of the apparatus 1702 and/or the processing system 1814 ofthe apparatus 1702′ configured to perform the functions recited by theaforementioned means. As described supra, the processing system 1814 mayinclude the TX Processor 368, the RX Processor 356, and thecontroller/processor 359. As such, in one configuration, theaforementioned means may be the TX Processor 368, the RX Processor 356,and the controller/processor 359 configured to perform the functionsrecited by the aforementioned means.

FIG. 19 is a flowchart 1900 of a method of wireless communication. Themethod may be performed by a central unit, such as an IAB node or basestation (e.g., the base station 102/180, 310, the IAB node 402, 606, thecentral unit 706, 806; the apparatus 2002/2002′; the processing system2114, which may include the memory 376 and which may be the entirecentral unit, IAB node or base station 310 or a component of the centralunit, IAB node or base station 310, such as the TX processor 316, the RXprocessor 370, and/or the controller/processor 375). The central unitmay communicate with a first node and a second node, such as an IAB nodeor UE. For example, the first node may be the parent node 702, 802, andthe second node may be the child node 704, 804. Alternatively, the firstnode may be the child node 704, 804, and the second node may be theparent node 702, 802. Optional aspects are illustrated in dashed lines.The method allows the central unit to provide more efficient capabilityto the first node for communicating with the second node based on amultiplexing capability of the first node using, e.g., SDM.

At 1902, the central unit may receive a report from a first node, wherethe report includes at least one multiplexing capability of the firstnode or includes at least one multiplexing capability condition for theat least one multiplexing capability of the first node. For example,1902 may be performed by receive report component 2008. For instance,referring to FIG. 8 , the central unit 806 may receive a report 808, 810respectively from a parent node 802 or a child node 804. The report maybe received from a child node, a parent node, or both a child node and aparent node. In an aspect, reports from a child node may be optional.One or more of the reports may include, but are not limited to,beam/channel quality measurements, CLI measurements, RRM measurements,traffic/load report, SDM FD or SDM HD capability and SDM FD or SDM HDconditions, e.g. what pairs of beams or pairs of links may betransmitted using SDM, and any limitation on the link-budget (e.g., maxTX or RX power). One or more of the reports may include a report of SIor cross-beam interference measurements.

At 1904, the central unit may transmit to a second node an indication ofthe at least one multiplexing capability or the at least onemultiplexing capability condition. For example, 1904 may be performed bycapability indication component 2010. For instance, referring to FIG. 8, when the CU 806 receives the report 810 from the child node 804, theCU may transmit to the parent node 802 an indication of the capabilityor conditions of the child node. The report 808 from the parent node 802may similarly include SDM capability and/or conditions of the parentnode, and the CU 806 may similarly transmit to the child node 804 anindication of the capability or conditions of the parent node.

At 1906, the central unit transmits to the first node a semi-staticresource allocation based on at least one multiplexing capability of thefirst node for communication of the first node with a second node. Thesemi-static resource allocation may be transmitted based on the reportreceived at 1902. The at least one multiplexing capability comprises atleast one of SDM or FDM, and the SDM includes at least one of SDM FD orSDM HD. For example, 1906 may be performed by transmit semi-staticresource component 2012. For instance, referring to FIG. 8 , the centralunit 806 may transmit a semi-static resource allocation 812 to one ormore nodes including the parent node 802 or child node 804 to use forcommunicating using SDM in response to receiving report 808 and/or 810.The one or more nodes may be one or more child nodes 804 and/or one ormore parent nodes 802. The semi-static resources may include, but arenot limited to allocation information for time-domain resources.

The at least one multiplexing capability is also with respect to one ormore transmission direction combinations of the first node. For example,the first node may include a MT and a DU, and the one or moretransmission direction combinations may comprise at least one of MTtransmission and DU transmission, MT transmission and DU reception, MTreception and DU transmission, or MT reception and DU reception. Forinstance, referring to FIG. 8 , the report 808, 810 may indicate SDM orFDM capability of the parent node or child node with respect totransmission-direction combinations including MT-TX/DU-TX (the MTtransmits while the DU transmits), MT-TX/DU-RX (the MT transmits whilethe DU receives), MT-RX/DU-TX (the MT receives while the DU transmits),and MT-RX/DU-RX (the MT receives while the DU receives).

The at least one multiplexing capability condition may comprise at leastone of: one or more beams to be used for SDM; or a link budget of thefirst node. For example, referring to FIG. 8 , if the SDM capability isconditional, the report 810 to the CU may include the SDM FD or SDM HDconditions of the child node (e.g. beams that may be used for SDM, linkbudget requirements, the links or beam pairs available for SDM, and/orthe physical channels available for SDM).

At 1908, the central unit transmits, to the first node, one or moreresource conditions for using allocated resources of the semi-staticresource allocation. The communication of the first node with the secondnode is based on the one or more resource conditions. For example, 1908may be performed by transmit conditions component 2014. For instance,referring to FIG. 8 , the central unit 806 may transmit conditions 814for use of resources to one or more nodes. The one or more nodes may beone or more child nodes 804 and/or one or more parent nodes 802. Atleast one of the semi-static resource allocation 812 or the conditions814 for use of resources may be based on the report 808, 810.

The one or more resource conditions may indicate whether the allocatedresources are conditional or unconditional for communication of thefirst node with the second node. For instance, referring to FIG. 8 , theconditions 814 may indicate whether a set of allocated time-domainresources may be used unconditionally or not for SDM Full-duplex orHalf-duplex operation. Conditions 814 may include the directionalconditions (D/U/F) described above, as well as additional conditions forconditional use. For example, in a case of conditional use, the CU 806may further indicate as conditions 814 various constraints such as thoseon modulation coding scheme (MCS, e.g. the maximum MCS used over theallocated resources), transmit (Tx) power (e.g. the maximum Tx powerthat may be used), receive (Rx) power (e.g. the maximum Rx power thatmay be used), TX/RX beam(s) that may be used (e.g. the subset of beamsor beam pairs/links that may be used), frequency-domain resources (e.g.the limited RBs that may be used over an indicated set of time domainresources in the semi-static resource allocation), reference signalconfiguration/resources (e.g. the specific tones or resources that DMRSor another reference signal may be transmitted), and timing reference(e.g. the Tx/Rx timing to be used for alignment with other simultaneouscommunications).

In one example, the first node may be a parent node and the second nodemay be a child node, and the one or more resource conditions mayidentify at least one expected behavior of the parent node with respectto the allocated resources for communicating with the child node. Theallocated resources may comprise one of hard resources or softresources. For instance, referring to FIG. 8 , semi-static resourceallocation 812 and/or conditions 814 may identify an expected behaviorof the parent node 802 as an alternative to aforementioned conflictresolution rules. For example, if the resource allocation for a same setof resources is (HARD∥HARD), the conditions 814 may indicate to theparent node 802 an expected behavior not to yield the resources for useby its children when the child node 804 has HD or FD capability. Inanother example, the conditions 814 may indicate to the parent node anexpected behavior not to refrain from using released soft resources whencommunicating with the child node.

In another example, the first node may be a child node and the secondnode may be a parent node, and the one or more resource conditions mayidentify at least one expected behavior of the child node with respectto the allocated resources for communicating with the parent node. Forinstance, referring to FIG. 8 , the conditions 814 may indicate to thechild node 804 an expected behavior not to refrain from using unreleased(or reclaimed) soft resources when communicating with its own childnodes or the parent node 802.

Finally, at 1910, the central unit may receive a change request from thefirst node to modify the semi-static resource allocation. The at leastone multiplexing capability may be enabled for the first node based onthe modified semi-static resource allocation. For example, 1910 may beperformed by receive change request component 2016. For instance,referring to FIG. 8 , the central unit 806 may receive a change request816, 818 respectively from the parent node 802 or child node 804 tomodify at least one of the semi-static resource allocation 812 or theconditions 814 for use of resources. The change request may be receivedfrom a child node, a parent node, or both a child node and a parentnode. In an aspect, the change request may include a request to enableor disable at least one of SDM FD or SDM HD.

FIG. 20 is a conceptual data flow diagram 2000 illustrating the dataflow between different means/components in an example apparatus 2002.The apparatus may be a CU (e.g. CU 806) in communication with a firstnode 2050 and a second node 2060. The first node may be, e.g., parentnode 802, and the second node may be, e.g., child node 804.Alternatively, the first may be, e.g., child node 804, and the secondnode may be, e.g., parent node 802.

The apparatus 2002 includes a reception component 2004 that isconfigured to receive communications from the first node 2050 and secondnode 2060. For example, the reception component may receive reports andchange requests from the first node and the second node. The apparatusalso includes a transmission component 2006 that is configured totransmit communications to the first node and the second node. Forexample, the transmission component may transmit semi-static resourceallocations and resource conditions to the first node and the secondnode.

The apparatus 2002 (e.g. the reception component 2004) includes areceive report component 2008 that is configured to receive a reportfrom a first node, where the report includes at least one multiplexingcapability of the first node or includes at least one multiplexingcapability condition for the at least one multiplexing capability of thefirst node, e.g., as described in connection with 1902. The apparatusmay include a capability indication component 2010 that is configured totransmit to a second node an indication of the at least one multiplexingcapability or the at least one multiplexing capability condition (basedon the report from receive report component 2008), e.g., as described inconnection with 1904. The apparatus includes a transmit semi-staticresource component 2012 that is configured to transmit to the first nodea semi-static resource allocation based on the at least one multiplexingcapability for communication of the first node with a second node, e.g.,as described in connection with 1906. The semi-static resourceallocation may also be transmitted based on the report from receivereport component 2008. The apparatus may include a transmit conditionscomponent 2014 that is configured to transmit, to the first node, one ormore resource conditions for using allocated resources of thesemi-static resource allocation, e.g., as described in connection with1908. The apparatus may include a receive change request component 2016that is configured to receive a change request from the first node tomodify the semi-static resource allocation, e.g., as described inconnection with 1910.

The apparatus may include additional components that perform each of theblocks of the algorithm in the aforementioned flowchart of FIG. 19 . Assuch, each block in the aforementioned flowchart of FIG. 19 may beperformed by a component and the apparatus may include one or more ofthose components. The components may be one or more hardware componentsspecifically configured to carry out the stated processes/algorithm,implemented by a processor configured to perform the statedprocesses/algorithm, stored within a computer-readable medium forimplementation by a processor, or some combination thereof.

FIG. 21 is a diagram 2100 illustrating an example of a hardwareimplementation for an apparatus 2002′ employing a processing system2114. The processing system 2114 may be implemented with a busarchitecture, represented generally by the bus 2124. The bus 2124 mayinclude any number of interconnecting buses and bridges depending on thespecific application of the processing system 2114 and the overalldesign constraints. The bus 2124 links together various circuitsincluding one or more processors and/or hardware components, representedby the processor 2104, the components 2004, 2006, 2008, 2010, 2012,2014, 2016 and the computer-readable medium/memory 2106. The bus 2124may also link various other circuits such as timing sources,peripherals, voltage regulators, and power management circuits, whichare well known in the art, and therefore, will not be described anyfurther.

The processing system 2114 may be coupled to a transceiver 2110. Thetransceiver 2110 is coupled to one or more antennas 2120. Thetransceiver 2110 provides a means for communicating with various otherapparatus over a transmission medium. The transceiver 2110 receives asignal from the one or more antennas 2120, extracts information from thereceived signal, and provides the extracted information to theprocessing system 2114, specifically the reception component 2004. Inaddition, the transceiver 2110 receives information from the processingsystem 2114, specifically the transmission component 2006, and based onthe received information, generates a signal to be applied to the one ormore antennas 2120. The processing system 2114 includes a processor 2104coupled to a computer-readable medium/memory 2106. The processor 2104 isresponsible for general processing, including the execution of softwarestored on the computer-readable medium/memory 2106. The software, whenexecuted by the processor 2104, causes the processing system 2114 toperform the various functions described supra for any particularapparatus. The computer-readable medium/memory 2106 may also be used forstoring data that is manipulated by the processor 2104 when executingsoftware. The processing system 2114 further includes at least one ofthe components 2004, 2006, 2008, 2010, 2012, 2014, 2016. The componentsmay be software components running in the processor 2104,resident/stored in the computer readable medium/memory 2106, one or morehardware components coupled to the processor 2104, or some combinationthereof. The processing system 2114 may be a component of a CU (e.g. CU706, 806 of an IAB node 606) or the base station 310 and may include thememory 376 and/or at least one of the TX processor 316, the RX processor370, and the controller/processor 375. Alternatively, the processingsystem 2114 may be the entire CU, IAB node, or base station (e.g., see310 of FIG. 3 ).

In one configuration, the apparatus 2002/2002′ for wirelesscommunication includes means for transmitting to the first node asemi-static resource allocation based on at least one multiplexingcapability of the first node for communication of the first node with asecond node; and means for transmitting, to the first node, one or moreresource conditions for using allocated resources of the semi-staticresource allocation; wherein the communication of the first node withthe second node is based on the one or more resource conditions; whereinthe at least one multiplexing capability comprises at least one ofSpatial Division Multiplexing (SDM) or Frequency Division Multiplexing(FDM), and wherein the SDM includes at least one of SDM Full Duplex (SDMFD) or SDM Half-Duplex (SDM HD); and wherein the at least onemultiplexing capability is with respect to one or more transmissiondirection combinations of the first node.

In one configuration, the apparatus 2002/2002′ may include means fortransmitting to the second node an indication of the at least onemultiplexing capability.

In one configuration, the apparatus 2002/2002′ may include means forreceiving a report from a first node, wherein the report includes the atleast one multiplexing capability of the first node or includes at leastone multiplexing capability condition for the at least one multiplexingcapability of the first node, and wherein the semi-static resourceallocation may be transmitted based on the report.

In one configuration, the apparatus 2002/2002′ may include means forreceiving a change request from the first node to modify the semi-staticresource allocation; wherein the at least one multiplexing capability isenabled for the first node based on the modified semi-static resourceallocation.

The aforementioned means may be one or more of the aforementionedcomponents of the apparatus 2002 and/or the processing system 2114 ofthe apparatus 2002′ configured to perform the functions recited by theaforementioned means. As described supra, the processing system 2114 mayinclude the TX Processor 316, the RX Processor 370, and thecontroller/processor 375. As such, in one configuration, theaforementioned means may be the TX Processor 316, the RX Processor 370,and the controller/processor 375 configured to perform the functionsrecited by the aforementioned means.

FIG. 22 is a flowchart 2200 of a method of wireless communication. Themethod may be performed by a first node, such as an IAB node or UE(e.g., the UE 104, 350, 514, the IAB node 402, 414, 416, 424, 426, 434,436, 501, 503, 506, 506, 510, 512, 516, 520, 605, 902, 906, the parentnode 702, 802, the child node 704, 804; the apparatus 2302/2302′; theprocessing system 2414, which may include the memory 360 and which maybe the entire IAB node or UE 350 or a component of the IAB node or UE350, such as the TX processor 368, the RX processor 356, and/or thecontroller/processor 359). The first node may communicate with a secondnode, such as another IAB node or UE. For example, the first node may bethe parent node 702, 802, and the second node may be the child node 704,804. Alternatively, the first node may be the child node 704, 804, andthe second node may be the parent node 702, 802. Optional aspects areillustrated in dashed lines. The method allows the first node to performmore efficient communication with the second node based on amultiplexing capability of the first node using, e.g., SDM.

At 2202, the first node may perform a local interference measurement ofone or more beams for communicating with the second node. For example,2202 may be performed by interference measurement component 2308. Forinstance, referring to FIG. 8 , a child node 804 may perform a localinterference measurement 805. For example, the child node 804 mayperform one or more of a self-interference measurement or a cross-beaminterference measurement. Performing an interference measurement mayinclude receiving a signal and determining the interference measurementbased on the received signal.

At 2204, the first node may transmit a report to a CU, where the reportincludes at least one multiplexing capability of the first node orincludes at least one multiplexing capability condition for the at leastone multiplexing capability of the first node. For example, 2204 may beperformed by transmission report component 2312. The at least onemultiplexing capability comprises at least one of SDM or FDM, and theSDM includes at least one of SDM FD or SDM HD. For instance, referringto FIG. 8 , the parent node 802 or the child node 804 may respectivelytransmit a report 808, 810 including a SDM FD or HD capability orconditions to a central unit 806. The report may be transmitted by achild node, a parent node, or both a child node and a parent node. In anaspect, reports transmitted by a child node may be optional.

The report may also include the local interference measurement. One ormore of the reports may include, but are not limited to beam/channelquality measurements, CLI measurements, RRM measurements, traffic/loadreport, SDM FD or SDM HD capability and SDM FD or SDM HD conditions,e.g. what pairs of beams or pairs of links may be transmitted using anSDM associated with them, and when there may be any limitation on thelink-budget (e.g., max TX or RX power). One or more of the reports mayinclude a report of SI or cross-beam interference measurements.

The at least one multiplexing capability is also with respect to one ormore transmission direction combinations of the first node. For example,the first node may include a MT and a DU, and the one or moretransmission direction combinations may comprise at least one of MTtransmission and DU transmission, MT transmission and DU reception, MTreception and DU transmission, or MT reception and DU reception. Forinstance, referring to FIG. 8 , the report 808, 810 may indicate SDM orFDM capability of the parent node or child node with respect totransmission-direction combinations including MT-TX/DU-TX (the MTtransmits while the DU transmits), MT-TX/DU-RX (the MT transmits whilethe DU receives), MT-RX/DU-TX (the MT receives while the DU transmits),and MT-RX/DU-RX (the MT receives while the DU receives).

In one example, the at least one multiplexing capability may be for SDMFD, and the one or more beams may comprise a transmission beam and areception beam of the first node. For instance, referring to FIG. 8 ,for SDM (FD) operation, the child node 804 may measure self-interferencefor different combinations of TX/RX beams.

In another example, the at least one multiplexing capability may be forSDM HD, and the one or more beams may comprise a plurality oftransmission beams of the first node or a plurality of reception beamsof the first node. For instance, referring to FIG. 8 , for SDM (HD)operation, the child node 804 may measure cross-beam interference, inwhich a transmission (or reception) over one beam of the child node mayinterfere with a transmission (or reception) over another beam of thechild node.

The at least one multiplexing capability condition may comprise at leastone of: one or more beams to be used for SDM; or a link budget of thefirst node. For example, referring to FIG. 8 , if the SDM capability isconditional, the report 810 to the CU may include the SDM FD or SDM HDconditions of the child node (e.g. beams that may be used for SDM, linkbudget requirements, the links or beam pairs available for SDM, and/orthe physical channels available for SDM).

At 2206, the first node receives a semi-static resource allocation fromthe CU based on the at least one multiplexing capability of the firstnode. For example, 2206 may be performed by receive semi-static resourcecomponent 2314. The semi-static resource allocation may also be receivedbased on the report transmitted at 2204. For instance, referring to FIG.8 , the parent node 802 or the child node 804 may receive a semi-staticresource allocation 812 from the central unit 806 for communicating witheach other using SDM in response to report 808 and/or 810.

At 2208, the first node may receive, from the CU, one or more resourceconditions for using allocated resources of the semi-static resourceallocation. For example, 2208 may be performed by receive conditionscomponent 2316. For instance, referring to FIG. 8 , the parent node 802or the child node 804 may receive conditions 814 for use of resourcesfrom the central unit 806. The conditions may be received by one or morenodes. The one or more nodes may be one or more child nodes and/or oneor more parent nodes. At least one of the semi-static resourceallocation or the conditions for use of resources may be based on thereport.

The one or more resource conditions may indicate whether the allocatedresources are conditional or unconditional for communicating with thesecond node. For instance, referring to FIG. 8 , the conditions 814 mayindicate whether a set of allocated time-domain resources may be usedunconditionally or not for SDM Full-duplex or Half-duplex operation.Conditions 814 may include the directional conditions (D/U/F) describedabove, as well as additional conditions for conditional use. Forexample, in a case of conditional use, the CU 806 may further indicateas conditions 814 various constraints such as those on modulation codingscheme (MCS, e.g. the maximum MCS used over the allocated resources),transmit (Tx) power (e.g. the maximum Tx power that may be used),receive (Rx) power (e.g. the maximum Rx power that may be used), TX/RXbeam(s) that may be used (e.g. the subset of beams or beam pairs/linksthat may be used), frequency-domain resources (e.g. the limited RBs thatmay be used over an indicated set of time domain resources in thesemi-static resource allocation), reference signalconfiguration/resources (e.g. the specific tones or resources that DMRSor another reference signal may be transmitted), and timing reference(e.g. the Tx/Rx timing to be used for alignment with other simultaneouscommunications).

In one example, the first node may be a parent node and the second nodemay be a child node, and the one or more resource conditions mayidentify at least one expected behavior of the parent node with respectto the allocated resources for communicating with the child node. Theallocated resources may comprise one of hard resources or softresources. For instance, referring to FIG. 8 , semi-static resourceallocation 812 and/or conditions 814 may identify an expected behaviorof the parent node 802 as an alternative to aforementioned conflictresolution rules. For example, if the resource allocation for a same setof resources is (HARD∥HARD), the conditions 814 may indicate to theparent node 802 an expected behavior not to yield the resources for useby its children when the child node 804 has HD or FD capability. Inanother example, the conditions 814 may indicate to the parent node anexpected behavior not to refrain from using released soft resources whencommunicating with the child node.

In another example, the first node may be a child node and the secondnode may be a parent node, and the one or more resource conditions mayidentify at least one expected behavior of the child node with respectto the allocated resources for communicating with the parent node. Forinstance, referring to FIG. 8 , the conditions 814 may indicate to thechild node 804 an expected behavior not to refrain from using unreleased(or reclaimed) soft resources when communicating with its own childnodes or the parent node 802.

At 2210, the first node may modify at least one of a transmission beamor a reception beam based on the local interference measurement. Forexample, 2210 may be performed by a modify beams component 2310. Forinstance, referring to FIG. 8 , the parent node 802 or the child node804 may modify, at 820 and 822 respectively, at least one of a transmitor a receive beam based on at least one of the semi-static resourceallocation 812 or the conditions 814 for use of resources, where thesemi-static resource allocation 812 or the conditions 814 may beindicated based on the report 810 sent to the CU 806 including the localinterference measurement 805. For example, the parent node 802 or thechild node 804 may modify beams by processing at least one of thesemi-static resource allocation or the conditions for use of resourcesto determine a modification and implementing the modification to the atleast one of a transmit or a receive beam.

At 2212, the first node communicates with a second node based on thesemi-static resource allocation. The communication with the second nodemay also be based on the one or more resource conditions. For example,2212 may be performed by establish FD component 2320. For instance,referring to FIG. 8 , the parent node 802 or the child node 804 mayestablish a FD connection and communicate with each other at 824 or 826using at least one of a hard resource or a soft resource based on atleast one of the semi-static resource allocation 812 or the conditions814 for use of resources received based on the report 810 to the CU 806.

Finally, at 2214, the first node transmits a change request to the CU tomodify the semi-static resource allocation. For example, 2214 may beperformed by transmit change request component 2318. For instance,referring to FIG. 8 , the parent node 802 or the child node 804 mayrespectively transmit a change request 816, 818 to the CU 806 to modifyat least one of the semi-static resource allocation 812 or theconditions 814 for use of resources. In an aspect, the change requestmay include a request to enable or disable at least one of SDM FD or SDMHD. The parent node and child node may subsequently communicate usingthe modified semi-static resource allocation (e.g. at 824 or 826).

FIG. 23 is a conceptual data flow diagram 2300 illustrating the dataflow between different means/components in an example apparatus 2302.The apparatus may be a first node in communication with a second node2350 and a CU 2360 (e.g. CU 806). The apparatus may be, e.g., parentnode 802, and the second node may be, e.g., child node 804.Alternatively, the apparatus may be, e.g., child node 804, and thesecond node may be, e.g., parent node 802.

The apparatus 2302 includes a reception component 2304 that isconfigured to receive communications from the second node 2350 and CU2360. For example, the reception component may receive semi-staticresource allocations from the CU and data from the second node. Theapparatus also includes a transmission component 2306 that is configuredto transmit communications to the second node and CU. For example, thetransmission component may transmit reports to the CU and data to thesecond node.

The apparatus 2302 may include an interference measurement component2308 that is configured to perform a local interference measurement ofone or more beams for communicating with the second node, e.g., asdescribed in connection with 2202. The apparatus may include a modifybeams component 2310 that is configured to modify at least one of atransmission beam or a reception beam based on the local interferencemeasurement, e.g., as described in connection with 2210. The apparatus(e.g. the transmission component 2306) may include a transmission reportcomponent 2312 that is configured to transmit a report to the CU, wherethe report includes at least one multiplexing capability of the firstnode or includes at least one multiplexing capability condition for theat least one multiplexing capability of the first node, e.g., asdescribed in connection with 2204. The apparatus (e.g. the receptioncomponent 2304) may include a receive semi-static resource component2314 that is configured to receive a semi-static resource allocationfrom the CU based on the at least one multiplexing capability (e.g.included in the report from transmission report component 1112), e.g.,as described in connection with 2206.

The apparatus 2302 (e.g. the reception component 2304) may include areceive conditions component 2316 that is configured to receive, fromthe CU 2360, one or more resource conditions for using allocatedresources of the semi-static resource allocation, e.g., as described inconnection with 2208. The apparatus (e.g. the transmission component2306) may include a transmit change request component 2318 that isconfigured to transmit a change request to the CU to modify thesemi-static resource allocation (received by receive conditionscomponent 2316), e.g., as described in connection with 2214. Theapparatus may include an establish FD component 2320 that is configuredto communicate with the second node 2350 based on the semi-staticresource allocation and on the one or more resource conditions (receivedby receive conditions component 2316), e.g., as described in connectionwith 2212.

The apparatus may include additional components that perform each of theblocks of the algorithm in the aforementioned flowchart of FIG. 22 . Assuch, each block in the aforementioned flowchart of FIG. 22 may beperformed by a component and the apparatus may include one or more ofthose components. The components may be one or more hardware componentsspecifically configured to carry out the stated processes/algorithm,implemented by a processor configured to perform the statedprocesses/algorithm, stored within a computer-readable medium forimplementation by a processor, or some combination thereof.

FIG. 24 is a diagram 2400 illustrating an example of a hardwareimplementation for an apparatus 2302′ employing a processing system2414. The processing system 2414 may be implemented with a busarchitecture, represented generally by the bus 2424. The bus 2424 mayinclude any number of interconnecting buses and bridges depending on thespecific application of the processing system 2414 and the overalldesign constraints. The bus 2424 links together various circuitsincluding one or more processors and/or hardware components, representedby the processor 2404, the components 2304, 2306, 2308, 2310, 2312,2314, 2316, 2318, 2320 and the computer-readable medium/memory 2406. Thebus 2424 may also link various other circuits such as timing sources,peripherals, voltage regulators, and power management circuits, whichare well known in the art, and therefore, will not be described anyfurther.

The processing system 2414 may be coupled to a transceiver 2410. Thetransceiver 2410 is coupled to one or more antennas 2420. Thetransceiver 2410 provides a means for communicating with various otherapparatus over a transmission medium. The transceiver 2410 receives asignal from the one or more antennas 2420, extracts information from thereceived signal, and provides the extracted information to theprocessing system 2414, specifically the reception component 2304. Inaddition, the transceiver 2410 receives information from the processingsystem 2414, specifically the transmission component 2306, and based onthe received information, generates a signal to be applied to the one ormore antennas 2420. The processing system 2414 includes a processor 2404coupled to a computer-readable medium/memory 2406. The processor 2404 isresponsible for general processing, including the execution of softwarestored on the computer-readable medium/memory 2406. The software, whenexecuted by the processor 2404, causes the processing system 2414 toperform the various functions described supra for any particularapparatus. The computer-readable medium/memory 2406 may also be used forstoring data that is manipulated by the processor 2404 when executingsoftware. The processing system 2414 further includes at least one ofthe components 2304, 2306, 2308, 2310, 2312, 2314, 2316, 2318, 2320. Thecomponents may be software components running in the processor 2404,resident/stored in the computer readable medium/memory 2406, one or morehardware components coupled to the processor 2404, or some combinationthereof. The processing system 2414 may be a component of an IAB node(e.g. IAB node 402) or the UE 350 and may include the memory 360 and/orat least one of the TX processor 368, the RX processor 356, and thecontroller/processor 359. Alternatively, the processing system 2414 maybe the entire IAB node or UE (e.g., see 350 of FIG. 3 ).

In one configuration, the apparatus 2302/2302′ for wirelesscommunication includes means for receiving a semi-static resourceallocation from a central unit (CU) based on at least one multiplexingcapability of the first node; means for communicating with a second nodebased on the semi-static resource allocation; and means for transmittinga change request to the CU to modify the semi-static resourceallocation; wherein the at least one multiplexing capability is enabledbased on the modified semi-static resource allocation; wherein the atleast one multiplexing capability comprises at least one of SpatialDivision Multiplexing (SDM) or Frequency Division Multiplexing (FDM),and wherein the SDM includes at least one of SDM Full Duplex (SDM FD) orSDM Half-Duplex (SDM HD); and wherein the at least one multiplexingcapability is with respect to one or more transmission directioncombinations of the first node.

In one configuration, the apparatus 2302/2302′ may include means forperforming a local interference measurement of one or more beams forcommunicating with the second node; and wherein the report includes thelocal interference measurement.

In one configuration, the apparatus 2302/2302′ may include means formodifying at least one of the transmission beam or the reception beambased on the local interference measurement.

In one configuration, the apparatus 2302/2302′ may include means fortransmitting a report to the CU, wherein the report may include the atleast one multiplexing capability of the first node or may include atleast one multiplexing capability condition for the at least onemultiplexing capability of the first node, and wherein the semi-staticresource allocation is received based on the report.

In one configuration, the apparatus 2302/2302′ may include means forreceiving, from the CU, one or more resource conditions for usingallocated resources of the semi-static resource allocation; wherein thecommunicating with the second node may be based on the one or moreresource conditions.

The aforementioned means may be one or more of the aforementionedcomponents of the apparatus 2302 and/or the processing system 2414 ofthe apparatus 2302′ configured to perform the functions recited by theaforementioned means. As described supra, the processing system 2414 mayinclude the TX Processor 368, the RX Processor 356, and thecontroller/processor 359. As such, in one configuration, theaforementioned means may be the TX Processor 368, the RX Processor 356,and the controller/processor 359 configured to perform the functionsrecited by the aforementioned means.

FIG. 25 is a flowchart 2500 of a method of wireless communication. Themethod may be performed by a central unit, such as an IAB node or basestation (e.g., the base station 102/180, 310, the IAB node 402, 606, thecentral unit 706, 806; the apparatus 2602/2602′; the processing system2714, which may include the memory 376 and which may be the entirecentral unit, IAB node or base station 310 or a component of the centralunit, IAB node or base station 310, such as the TX processor 316, the RXprocessor 370, and/or the controller/processor 375). The central unitmay communicate with a first node and a second node, such as an IAB nodeor UE. For example, the first node may be the parent node 702, 802, andthe second node may be the child node 704, 804. Alternatively, the firstnode may be the child node 704, 804, and the second node may be theparent node 702, 802. Optional aspects are illustrated in dashed lines.The method allows the central unit to provide more efficient capabilityto the first node for communicating with the second node based on amultiplexing capability of the first node using, e.g., SDM.

At 2502, the central unit may receive a report from a first node, wherethe report may include at least one multiplexing capability of the firstnode or may include at least one multiplexing capability condition forthe at least one multiplexing capability of the first node. For example,2502 may be performed by receive report component 2608. For instance,referring to FIG. 8 , the central unit 806 may receive a report 808, 810respectively from a parent node 802 or a child node 804. The report maybe received from a child node, a parent node, or both a child node and aparent node. In an aspect, reports from a child node may be optional.One or more of the reports may include, but are not limited to,beam/channel quality measurements, CLI measurements, RRM measurements,traffic/load report, SDM FD or SDM HD capability and SDM FD or SDM HDconditions, e.g. what pairs of beams or pairs of links may betransmitted using SDM, and any limitation on the link-budget (e.g., maxTX or RX power). One or more of the reports may include a report of SIor cross-beam interference measurements.

At 2504, the central unit may transmit to a second node an indication ofthe at least one multiplexing capability. For example, 2504 may beperformed by capability indication component 2610. For instance,referring to FIG. 8 , when the CU 806 receives the report 810 from thechild node 804, the CU may transmit to the parent node 802 an indicationof the capability or conditions of the child node. The report 808 fromthe parent node 802 may similarly include SDM capability and/orconditions of the parent node, and the CU 806 may similarly transmit tothe child node 804 an indication of the capability or conditions of theparent node.

At 2506, the central unit transmits to the first node a semi-staticresource allocation based on at least one multiplexing capability of thefirst node for communication of the first node with a second node. Thesemi-static resource allocation may be transmitted based on the reportreceived at 2502. The at least one multiplexing capability comprises atleast one of SDM or FDM, and the SDM includes at least one of SDM FD orSDM HD. For example, 2506 may be performed by transmit semi-staticresource component 2612. For instance, referring to FIG. 8 , the centralunit 806 may transmit a semi-static resource allocation 812 to one ormore nodes including the parent node 802 or child node 804 to use forcommunicating using SDM in response to receiving report 808 and/or 810.The one or more nodes may be one or more child nodes 804 and/or one ormore parent nodes 802. The semi-static resources may include, but arenot limited to allocation information for time-domain resources.

The at least one multiplexing capability is also with respect to one ormore transmission direction combinations of the first node. For example,the first node may include a MT and a DU, and the one or moretransmission direction combinations may comprise at least one of MTtransmission and DU transmission, MT transmission and DU reception, MTreception and DU transmission, or MT reception and DU reception. Forinstance, referring to FIG. 8 , the report 808, 810 may indicate SDM orFDM capability of the parent node or child node with respect totransmission-direction combinations including MT-TX/DU-TX (the MTtransmits while the DU transmits), MT-TX/DU-RX (the MT transmits whilethe DU receives), MT-RX/DU-TX (the MT receives while the DU transmits),and MT-RX/DU-RX (the MT receives while the DU receives).

The at least one multiplexing capability condition may comprise at leastone of: one or more beams to be used for SDM; or a link budget of thefirst node. For example, referring to FIG. 8 , if the SDM capability isconditional, the report 810 to the CU may include the SDM FD or SDM HDconditions of the child node (e.g. beams that may be used for SDM, linkbudget requirements, the links or beam pairs available for SDM, and/orthe physical channels available for SDM).

At 2508, the central unit may transmit, to the first node, one or moreresource conditions for using allocated resources of the semi-staticresource allocation. The communication of the first node with the secondnode may be based on the one or more resource conditions. For example,2508 may be performed by transmit conditions component 2614. Forinstance, referring to FIG. 8 , the central unit 806 may transmitconditions 814 for use of resources to one or more nodes. The one ormore nodes may be one or more child nodes 804 and/or one or more parentnodes 802. At least one of the semi-static resource allocation 812 orthe conditions 814 for use of resources may be based on the report 808,810.

The one or more resource conditions may indicate whether the allocatedresources are conditional or unconditional for communication of thefirst node with the second node. For instance, referring to FIG. 8 , theconditions 814 may indicate whether a set of allocated time-domainresources may be used unconditionally or not for SDM Full-duplex orHalf-duplex operation. Conditions 814 may include the directionalconditions (D/U/F) described above, as well as additional conditions forconditional use. For example, in a case of conditional use, the CU 806may further indicate as conditions 814 various constraints such as thoseon modulation coding scheme (MCS, e.g. the maximum MCS used over theallocated resources), transmit (Tx) power (e.g. the maximum Tx powerthat may be used), receive (Rx) power (e.g. the maximum Rx power thatmay be used), TX/RX beam(s) that may be used (e.g. the subset of beamsor beam pairs/links that may be used), frequency-domain resources (e.g.the limited RBs that may be used over an indicated set of time domainresources in the semi-static resource allocation), reference signalconfiguration/resources (e.g. the specific tones or resources that DMRSor another reference signal may be transmitted), and timing reference(e.g. the Tx/Rx timing to be used for alignment with other simultaneouscommunications).

In one example, the first node may be a parent node and the second nodemay be a child node, and the one or more resource conditions mayidentify at least one expected behavior of the parent node with respectto the allocated resources for communicating with the child node. Theallocated resources may comprise one of hard resources or softresources. For instance, referring to FIG. 8 , semi-static resourceallocation 812 and/or conditions 814 may identify an expected behaviorof the parent node 802 as an alternative to aforementioned conflictresolution rules. For example, if the resource allocation for a same setof resources is (HARD∥HARD), the conditions 814 may indicate to theparent node 802 an expected behavior not to yield the resources for useby its children when the child node 804 has HD or FD capability. Inanother example, the conditions 814 may indicate to the parent node anexpected behavior not to refrain from using released soft resources whencommunicating with the child node.

In another example, the first node may be a child node and the secondnode may be a parent node, and the one or more resource conditions mayidentify at least one expected behavior of the child node with respectto the allocated resources for communicating with the parent node. Forinstance, referring to FIG. 8 , the conditions 814 may indicate to thechild node 804 an expected behavior not to refrain from using unreleased(or reclaimed) soft resources when communicating with its own childnodes or the parent node 802.

Finally, at 2510, the central unit receives a change request from thefirst node to modify the semi-static resource allocation. For example,2510 may be performed by receive change request component 2616. Forinstance, referring to FIG. 8 , the central unit 806 may receive achange request 816, 818 respectively from the parent node 802 or childnode 804 to modify at least one of the semi-static resource allocation812 or the conditions 814 for use of resources. The change request maybe received from a child node, a parent node, or both a child node and aparent node. In an aspect, the change request may include a request toenable or disable at least one of SDM FD or SDM HD.

FIG. 26 is a conceptual data flow diagram 2600 illustrating the dataflow between different means/components in an example apparatus 2602.The apparatus may be a CU (e.g. CU 806) in communication with a firstnode 2650 and a second node 2660. The first node may be, e.g., parentnode 802, and the second node may be, e.g., child node 804.Alternatively, the first may be, e.g., child node 804, and the secondnode may be, e.g., parent node 802.

The apparatus 2602 includes a reception component 2604 that isconfigured to receive communications from the first node 2650 and secondnode 2660. For example, the reception component may receive reports andchange requests from the first node and the second node. The apparatusalso includes a transmission component 2606 that is configured totransmit communications to the first node and the second node. Forexample, the transmission component may transmit semi-static resourceallocations and resource conditions to the first node and the secondnode.

The apparatus 2602 (e.g. the reception component 2604) includes areceive report component 2608 that is configured to receive a reportfrom a first node, where the report includes at least one multiplexingcapability of the first node or includes at least one multiplexingcapability condition for the at least one multiplexing capability of thefirst node, e.g., as described in connection with 2502. The apparatusmay include a capability indication component 2610 that is configured totransmit to a second node an indication of the at least one multiplexingcapability or the at least one multiplexing capability condition (basedon the report from receive report component 2608), e.g., as described inconnection with 2504. The apparatus includes a transmit semi-staticresource component 2612 that is configured to transmit to the first nodea semi-static resource allocation based on the at least one multiplexingcapability for communication of the first node with a second node, e.g.,as described in connection with 2506. The semi-static resourceallocation may also be transmitted based on the report from receivereport component 2608. The apparatus may include a transmit conditionscomponent 2614 that is configured to transmit, to the first node, one ormore resource conditions for using allocated resources of thesemi-static resource allocation, e.g., as described in connection with2508. The apparatus may include a receive change request component 2616that is configured to receive a change request from the first node tomodify the semi-static resource allocation, e.g., as described inconnection with 2510.

The apparatus may include additional components that perform each of theblocks of the algorithm in the aforementioned flowchart of FIG. 25 . Assuch, each block in the aforementioned flowchart of FIG. 25 may beperformed by a component and the apparatus may include one or more ofthose components. The components may be one or more hardware componentsspecifically configured to carry out the stated processes/algorithm,implemented by a processor configured to perform the statedprocesses/algorithm, stored within a computer-readable medium forimplementation by a processor, or some combination thereof.

FIG. 27 is a diagram 2700 illustrating an example of a hardwareimplementation for an apparatus 2602′ employing a processing system2714. The processing system 2714 may be implemented with a busarchitecture, represented generally by the bus 2724. The bus 2724 mayinclude any number of interconnecting buses and bridges depending on thespecific application of the processing system 2714 and the overalldesign constraints. The bus 2724 links together various circuitsincluding one or more processors and/or hardware components, representedby the processor 2704, the components 2604, 2606, 2608, 2610, 2612,2614, 2616 and the computer-readable medium/memory 2706. The bus 2724may also link various other circuits such as timing sources,peripherals, voltage regulators, and power management circuits, whichare well known in the art, and therefore, will not be described anyfurther.

The processing system 2714 may be coupled to a transceiver 2710. Thetransceiver 2710 is coupled to one or more antennas 2720. Thetransceiver 2710 provides a means for communicating with various otherapparatus over a transmission medium. The transceiver 2710 receives asignal from the one or more antennas 2720, extracts information from thereceived signal, and provides the extracted information to theprocessing system 2714, specifically the reception component 2604. Inaddition, the transceiver 2710 receives information from the processingsystem 2714, specifically the transmission component 2606, and based onthe received information, generates a signal to be applied to the one ormore antennas 2720. The processing system 2714 includes a processor 2704coupled to a computer-readable medium/memory 2706. The processor 2704 isresponsible for general processing, including the execution of softwarestored on the computer-readable medium/memory 2706. The software, whenexecuted by the processor 2704, causes the processing system 2714 toperform the various functions described supra for any particularapparatus. The computer-readable medium/memory 2706 may also be used forstoring data that is manipulated by the processor 2704 when executingsoftware. The processing system 2714 further includes at least one ofthe components 2604, 2606, 2608, 2610, 2612, 2614, 2616. The componentsmay be software components running in the processor 2704,resident/stored in the computer readable medium/memory 2706, one or morehardware components coupled to the processor 2704, or some combinationthereof. The processing system 2714 may be a component of a CU (e.g. CU706, 806 of an IAB node 606) or the base station 310 and may include thememory 376 and/or at least one of the TX processor 316, the RX processor370, and the controller/processor 375. Alternatively, the processingsystem 2714 may be the entire CU, IAB node, or base station (e.g., see310 of FIG. 3 ).

In one configuration, the apparatus 2602/2602′ for wirelesscommunication includes means for transmitting to the first node asemi-static resource allocation based on at least one multiplexingcapability of the first node for communication of the first node with asecond node; and means for receiving a change request from the firstnode to modify the semi-static resource allocation; wherein the at leastone multiplexing capability comprises at least one of Spatial DivisionMultiplexing (SDM) or Frequency Division Multiplexing (FDM), and whereinthe SDM includes at least one of SDM Full Duplex (SDM FD) or SDMHalf-Duplex (SDM HD); and wherein the at least one multiplexingcapability is with respect to one or more transmission directioncombinations of the first node.

In one configuration, the apparatus 2602/2602′ may include means fortransmitting to the second node an indication of the at least onemultiplexing capability.

In one configuration, the apparatus 2602/2602′ may include means forreceiving a report from a first node, wherein the report includes the atleast one multiplexing capability of the first node or includes at leastone multiplexing capability condition for the at least one multiplexingcapability of the first node, and wherein the semi-static resourceallocation may be transmitted based on the report.

In one configuration, the apparatus 2602/2602′ may include means fortransmitting, to the first node, one or more resource conditions forusing allocated resources of the semi-static resource allocation;wherein the communication of the first node with the second node may bebased on the one or more resource conditions.

The aforementioned means may be one or more of the aforementionedcomponents of the apparatus 2602 and/or the processing system 2714 ofthe apparatus 2602′ configured to perform the functions recited by theaforementioned means. As described supra, the processing system 2714 mayinclude the TX Processor 316, the RX Processor 370, and thecontroller/processor 375. As such, in one configuration, theaforementioned means may be the TX Processor 316, the RX Processor 370,and the controller/processor 375 configured to perform the functionsrecited by the aforementioned means.

Accordingly, aspects of the present disclosure support efficient SDMoperation in IAB networks. For example, CU devices may provide for moreefficient performance of SDM operations for communications between theCU and both parent nodes and child nodes by providing resourceallocations and conditions for use of resources in response to reportsby the parent node and/or child node. Similarly, the parent nodes andchild nodes may more efficiently perform SDM operations forcommunications between the parent nodes and/or child nodes and the CUbased on the resource allocations and by following the conditions foruse of resources. The parent nodes and child nodes may also moreefficiently perform SDM operations for communications between the parentnodes and/or child nodes and the CU by sending change requests to the CUwhen beams, link budget constraints, or other configurations change. TheCU may similarly provide for more efficient performance of SDMoperations for communications between the CU and both parent nodes andchild nodes by sending new resource allocations in response to thechange requests in support of SDM operations.

Moreover, by coordinating with the CU regarding FD/HD capabilities, anJAB node may avoid making assumptions about other node capabilities,such as half-duplex constraints. For example, knowledge of TDM, SDM FD,and SDM HD capabilities for a given JAB node may allow for greaterspectral efficiency and/or greater capacity in wireless communication.Accordingly, the aspects described herein further provide forcommunication of TDM, SDM FD, and SDM HD capabilities between devices totake advantage of the greater spectral efficiency and/or greatercapacity of a particular IAB node. With some coordination or fullcoordination between an JAB node and the CU, which may configure andmanage semi-static resource allocations for the JAB node, JAB nodes andCUs may achieve efficient SDM(FD/HD) operation and improved resourceutilization.

It is understood that the specific order or hierarchy of blocks in theprocesses/flowcharts disclosed is an illustration of example approaches.Based upon design preferences, it is understood that the specific orderor hierarchy of blocks in the processes/flowcharts may be rearranged.Further, some blocks may be combined or omitted. The accompanying methodclaims present elements of the various blocks in a sample order, and arenot meant to be limited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in theart to practice the various aspects described herein. Variousmodifications to these aspects will be readily apparent to those skilledin the art, and the generic principles defined herein may be applied toother aspects. Thus, the claims are not intended to be limited to theaspects shown herein, but is to be accorded the full scope consistentwith the language claims, wherein reference to an element in thesingular is not intended to mean “one and only one” unless specificallyso stated, but rather “one or more.” The word “exemplary” is used hereinto mean “serving as an example, instance, or illustration.” Any aspectdescribed herein as “exemplary” is not necessarily to be construed aspreferred or advantageous over other aspects. Unless specifically statedotherwise, the term “some” refers to one or more. Combinations such as“at least one of A, B, or C,” “one or more of A, B, or C,” “at least oneof A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or anycombination thereof” include any combination of A, B, and/or C, and mayinclude multiples of A, multiples of B, or multiples of C. Specifically,combinations such as “at least one of A, B, or C,” “one or more of A, B,or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and“A, B, C, or any combination thereof” may be A only, B only, C only, Aand B, A and C, B and C, or A and B and C, where any such combinationsmay contain one or more member or members of A, B, or C. All structuraland functional equivalents to the elements of the various aspectsdescribed throughout this disclosure that are known or later come to beknown to those of ordinary skill in the art are expressly incorporatedherein by reference and are intended to be encompassed by the claims.Moreover, nothing disclosed herein is intended to be dedicated to thepublic regardless of whether such disclosure is explicitly recited inthe claims. The words “module,” “mechanism,” “element,” “device,” andthe like may not be a substitute for the word “means.” As such, no claimelement is to be construed as a means plus function unless the elementis expressly recited using the phrase “means for.”

What is claimed is:
 1. A method of wireless communication of a firstnode, comprising: performing a local interference measurement of one ormore beams for communicating with a second node, wherein the localinterference measurement measures transmit beams and receive beams atthe first node to determine at least one multiplexing capability of thefirst node; receiving a semi-static resource allocation from a centralunit (CU) based on the at least one multiplexing capability of the firstnode, wherein the first node includes a mobile terminal (MT) and adistributed unit (DU); receiving, from the CU, one or more resourceconditions for using allocated resources of the semi-static resourceallocation; and communicating with a second node based on thesemi-static resource allocation and the one or more resource conditions,wherein the one or more resource conditions indicate whether theallocated resources are conditional or unconditional for communicatingwith the second node; wherein the at least one multiplexing capabilityof the first node is with respect to one or more transmission directioncombinations of the first node, the one or more transmission directioncombinations comprising at least one of MT transmission and DUtransmission, MT transmission and DU reception, MT reception and DUtransmission, or MT reception and DU reception.
 2. The method of claim1, further comprising: transmitting a report to the CU, wherein thereport includes the at least one multiplexing capability of the firstnode or includes at least one multiplexing capability condition for theat least one multiplexing capability of the first node; wherein thesemi-static resource allocation is received based on the report.
 3. Themethod of claim 2, wherein the report includes the local interferencemeasurement.
 4. The method of claim 3, wherein the at least onemultiplexing capability is for SDM FD, and the one or more beamscomprise a transmission beam and a reception beam of the first node. 5.The method of claim 3, wherein the at least one multiplexing capabilityis for SDM HD, and the one or more beams comprise a plurality oftransmission beams of the first node or a plurality of reception beamsof the first node.
 6. The method of claim 2, wherein the at least onemultiplexing capability condition comprises at least one of: one or morebeams to be used for SDM; or a link budget of the first node.
 7. Themethod of claim 1, wherein the first node is a parent node and thesecond node is a child node, and wherein the one or more resourceconditions identify at least one expected behavior of the parent nodewith respect to the allocated resources for communicating with the childnode.
 8. The method of claim 7, wherein the allocated resources compriseone of hard resources or soft resources.
 9. The method of claim 1,wherein the first node is a child node and the second node is a parentnode, and wherein the one or more resource conditions identify at leastone expected behavior of the child node with respect to the allocatedresources for communicating with the parent node.
 10. The method ofclaim 1, further comprising: transmitting a change request to the CU tomodify the semi-static resource allocation; wherein the at least onemultiplexing capability is enabled based on the modified semi-staticresource allocation.
 11. A method of wireless communication at a centralunit (CU), comprising: receiving a report from a first node comprising alocal interference measurement of one or more beams for communicatingwith a second node, wherein the local interference measurement comprisesmeasurements of transmit beams and receive beams at the first node todetermine at least one multiplexing capability of the first node;transmitting to the first node a semi-static resource allocation basedon the at least one multiplexing capability of the first node forcommunication of the first node with the second node, wherein the firstnode includes a mobile terminal (MT) and a distributed unit (DU); andtransmitting, to the first node, one or more resource conditions forusing allocated resources of the semi-static resource allocation,wherein the communication of the first node with the second node isbased on the one or more resource conditions, wherein the one or moreresource conditions indicate whether the allocated resources areconditional or unconditional for the communication of the first nodewith the second node; wherein the at least one multiplexing capabilityof the first node is with respect to one or more transmission directioncombinations of the first node, the one or more transmission directioncombinations comprise at least one of MT transmission and DUtransmission, MT transmission and DU reception, MT reception and DUtransmission, or MT reception and DU reception.
 12. The method of claim11, further comprising: transmitting to the second node an indication ofthe at least one multiplexing capability.
 13. The method of claim 11,wherein the report includes the at least one multiplexing capability ofthe first node or includes at least one multiplexing capabilitycondition for the at least one multiplexing capability of the firstnode; and wherein the semi-static resource allocation is transmittedbased on the report.
 14. The method of claim 13, wherein the at leastone multiplexing capability condition comprises at least one of: one ormore beams to be used for SDM; or a link budget of the first node. 15.The method of claim 11, wherein the first node is a parent node and thesecond node is a child node, and wherein the one or more resourceconditions identify at least one expected behavior of the parent nodewith respect to the allocated resources for communicating with the childnode.
 16. The method of claim 15, wherein the allocated resourcescomprise one of hard resources or soft resources.
 17. The method ofclaim 11, wherein the first node is a child node and the second node isa parent node, and wherein the one or more resource conditions identifyat least one expected behavior of the child node with respect to theallocated resources for communicating with the parent node.
 18. Themethod of claim 11, further comprising: receiving a change request fromthe first node to modify the semi-static resource allocation; whereinthe at least one multiplexing capability is enabled for the first nodebased on the modified semi-static resource allocation.
 19. An apparatusfor wireless communication, the apparatus being a first node,comprising: means for performing a local interference measurement of oneor more beams for communicating with a second node, wherein the localinterference measurement measures transmit beams and receive beams atthe first node to determine at least one multiplexing capability of thefirst node; means for receiving a semi-static resource allocation from acentral unit (CU) based on the at least one multiplexing capability ofthe first node, wherein the first node includes a mobile terminal (MT)and a distributed unit (DU); wherein the means for receiving is furtherconfigured to receive, from the CU, one or more resource conditions forusing allocated resources of the semi-static resource allocation; andmeans for communicating with a second node based on the semi-staticresource allocation and the one or more resource conditions, wherein theone or more resource conditions indicate whether the allocated resourcesare conditional or unconditional for communicating with the second node;wherein the at least one multiplexing capability of the first node iswith respect to one or more transmission direction combinations of thefirst node, the one or more transmission direction combinations compriseat least one of MT transmission and DU transmission, MT transmission andDU reception, MT reception and DU transmission, or MT reception and DUreception.
 20. The apparatus of claim 19, further comprising: means fortransmitting a report to the CU, wherein the report includes the atleast one multiplexing capability of the first node or includes at leastone multiplexing capability condition for the at least one multiplexingcapability of the first node; wherein the semi-static resourceallocation is received based on the report.
 21. The apparatus of claim20, wherein the report includes the local interference measurement. 22.The apparatus of claim 21, wherein the at least one multiplexingcapability is for SDM FD, and the one or more beams comprise atransmission beam and a reception beam of the first node.
 23. Theapparatus of claim 19, further comprising: means for transmitting achange request to the CU to modify the semi-static resource allocation;wherein the at least one multiplexing capability is enabled based on themodified semi-static resource allocation.
 24. An apparatus for wirelesscommunication, the apparatus being a central unit (CU), comprising:means for receiving a report from a first node comprising a localinterference measurement of one or more beams for communicating with asecond node, wherein the local interference measurement comprisesmeasurements of transmit beams and receive beams at the first node todetermine at least one multiplexing capability of the first node; andmeans for transmitting to the first node a semi-static resourceallocation based on the at least one multiplexing capability of thefirst node for communication of the first node with the second node,wherein the first node includes a mobile terminal (MT) and a distributedunit (DU); wherein the means for transmitting is further configured totransmit, to the first node, one or more resource conditions for usingallocated resources of the semi-static resource allocation, wherein thecommunication of the first node with the second node is based on the oneor more resource conditions, wherein the one or more resource conditionsindicate whether the allocated resources are conditional orunconditional for the communication of the first node with the secondnode; wherein the at least one multiplexing capability of the first nodeis with respect to one or more transmission direction combinations ofthe first node, the one or more transmission direction combinationscomprise at least one of MT transmission and DU transmission, MTtransmission and DU reception, MT reception and DU transmission, or MTreception and DU reception.
 25. The apparatus of claim 24, wherein themeans for transmitting is further configured to transmit to the secondnode an indication of the at least one multiplexing capability.
 26. Theapparatus of claim 24, wherein the report includes the at least onemultiplexing capability of the first node or includes at least onemultiplexing capability condition for the at least one multiplexingcapability of the first node; and wherein the semi-static resourceallocation is transmitted based on the report.
 27. The apparatus ofclaim 24, further comprising: means for receiving a change request fromthe first node to modify the semi-static resource allocation; whereinthe at least one multiplexing capability is enabled for the first nodebased on the modified semi-static resource allocation.
 28. An apparatusfor wireless communication, the apparatus being a first node,comprising: a memory; and at least one processor coupled to the memoryand configured to: perform a local interference measurement of one ormore beams for communicating with a second node, wherein the localinterference measurement measures transmit beams and receive beams atthe first node to determine at least one multiplexing capability of thefirst node; receive a semi-static resource allocation from a centralunit (CU) based on the at least one multiplexing capability of the firstnode, wherein the first node includes a mobile terminal (MT) and adistributed unit (DU); receive, from the CU, one or more resourceconditions for using allocated resources of the semi-static resourceallocation; and communicate with a second node based on the semi-staticresource allocation and the one or more resource conditions, wherein theone or more resource conditions indicate whether the allocated resourcesare conditional or unconditional for communicating with the second node;wherein the at least one multiplexing capability of the first node iswith respect to one or more transmission direction combinations of thefirst node, the one or more transmission direction combinations compriseat least one of MT transmission and DU transmission, MT transmission andDU reception, MT reception and DU transmission, or MT reception and DUreception.
 29. The apparatus of claim 28, wherein the at least oneprocessor is further configured to: transmit a report to the CU, whereinthe report includes the at least one multiplexing capability of thefirst node or includes at least one multiplexing capability conditionfor the at least one multiplexing capability of the first node; whereinthe semi-static resource allocation is received based on the report. 30.The apparatus of claim 29, wherein the report includes the localinterference measurement.
 31. The apparatus of claim 30, wherein the atleast one multiplexing capability is for SDM FD, and the one or morebeams comprise a transmission beam and a reception beam of the firstnode.
 32. The apparatus of claim 30, wherein the at least onemultiplexing capability is for SDM HD, and the one or more beamscomprise a plurality of transmission beams of the first node or aplurality of reception beams of the first node.
 33. The apparatus ofclaim 29, wherein the at least one multiplexing capability conditioncomprises at least one of: one or more beams to be used for SDM; or alink budget of the first node.
 34. The apparatus of claim 28, whereinthe first node is a parent node and the second node is a child node, andwherein the one or more resource conditions identify at least oneexpected behavior of the parent node with respect to the allocatedresources for communicating with the child node.
 35. The apparatus ofclaim 34, wherein the allocated resources comprise one of hard resourcesor soft resources.
 36. The apparatus of claim 28, wherein the first nodeis a child node and the second node is a parent node, and wherein theone or more resource conditions identify at least one expected behaviorof the child node with respect to the allocated resources forcommunicating with the parent node.
 37. The apparatus of claim 28,wherein the at least one processor is further configured to: transmit achange request to the CU to modify the semi-static resource allocation;wherein the at least one multiplexing capability is enabled based on themodified semi-static resource allocation.
 38. An apparatus for wirelesscommunication, the apparatus being a central unit (CU), comprising: amemory; and at least one processor coupled to the memory and configuredto: receive a report from a first node comprising a local interferencemeasurement of one or more beams for communicating with a second node,wherein the local interference measurement comprises measurements oftransmit beams and receive beams at the first node to determine at leastone multiplexing capability of the first node; transmit to the firstnode a semi-static resource allocation based on the at least onemultiplexing capability of the first node for communication of the firstnode with the second node, wherein the first node includes a mobileterminal (MT) and a distributed unit (DU); and transmit, to the firstnode, one or more resource conditions for using allocated resources ofthe semi-static resource allocation, wherein the communication of thefirst node with the second node is based on the one or more resourceconditions, wherein the one or more resource conditions indicate whetherthe allocated resources are conditional or unconditional for thecommunication of the first node with the second node; wherein the atleast one multiplexing capability of the first node is with respect toone or more transmission direction combinations of the first node, theone or more transmission direction combinations comprise at least one ofMT transmission and DU transmission, MT transmission and DU reception,MT reception and DU transmission, or MT reception and DU reception. 39.The apparatus of claim 38, wherein the at least one processor is furtherconfigured to: transmit to the second node an indication of the at leastone multiplexing capability.
 40. The apparatus of claim 38, wherein thereport includes the at least one multiplexing capability of the firstnode or includes at least one multiplexing capability condition for theat least one multiplexing capability of the first node; and wherein thesemi-static resource allocation is transmitted based on the report. 41.The apparatus of claim 40, wherein the at least one multiplexingcapability condition comprises at least one of: one or more beams to beused for SDM; or a link budget of the first node.
 42. The apparatus ofclaim 38, wherein the first node is a parent node and the second node isa child node, and wherein the one or more resource conditions identifyat least one expected behavior of the parent node with respect to theallocated resources for communicating with the child node.
 43. Theapparatus of claim 42, wherein the allocated resources comprise one ofhard resources or soft resources.
 44. The apparatus of claim 38, whereinthe first node is a child node and the second node is a parent node, andwherein the one or more resource conditions identify at least oneexpected behavior of the child node with respect to the allocatedresources for communicating with the parent node.
 45. The apparatus ofclaim 38, wherein the at least one processor is further configured to:receive a change request from the first node to modify the semi-staticresource allocation; wherein the at least one multiplexing capability isenabled for the first node based on the modified semi-static resourceallocation.
 46. A non-transitory computer-readable medium storingcomputer executable code, the code when executed by a processor causethe processor to: perform a local interference measurement of one ormore beams for communicating with a second node, wherein the localinterference measurement measures transmit beams and receive beams at afirst node to determine at least one multiplexing capability of thefirst node; receive a semi-static resource allocation from a centralunit (CU) based on the at least one multiplexing capability of a firstnode, wherein the first node includes a mobile terminal (MT) and adistributed unit (DU); receive, from the CU, one or more resourceconditions for using allocated resources of the semi-static resourceallocation; and communicate with a second node based on the semi-staticresource allocation and the one or more resource conditions, wherein theone or more resource conditions indicate whether the allocated resourcesare conditional or unconditional for communicating with the second node;wherein the at least one multiplexing capability of the first node iswith respect to one or more transmission direction combinations of thefirst node, the one or more transmission direction combinations compriseat least one of MT transmission and DU transmission, MT transmission andDU reception, MT reception and DU transmission, or MT reception and DUreception.
 47. A non-transitory computer-readable medium storingcomputer executable code, the code when executed by a processor causethe processor to: receive a report from a first node comprising a localinterference measurement of one or more beams for communicating with asecond node, wherein the local interference measurement comprisesmeasurements of transmit beams and receive beams at the first node todetermine at least one multiplexing capability of the first node;transmit to the first node a semi-static resource allocation based onthe at least one multiplexing capability of the first node forcommunication of the first node with the second node, wherein the firstnode includes a mobile terminal (MT) and a distributed unit (DU); andtransmit, to the first node, one or more resource conditions for usingallocated resources of the semi-static resource allocation, wherein thecommunication of the first node with the second node is based on the oneor more resource conditions, wherein the one or more resource conditionsindicate whether the allocated resources are conditional orunconditional for the communication of the first node with the secondnode; wherein the at least one multiplexing capability of the first nodeis with respect to one or more transmission direction combinations ofthe first node, the one or more transmission direction combinationscomprise at least one of MT transmission and DU transmission, MTtransmission and DU reception, MT reception and DU transmission, or MTreception and DU reception.